If the list is coming back to life, then I've got a weird but hopefully simple problem for you:<div><br></div><div>I've got a Synology DiskStation DS209 NAS that's giving me erroneous free space readings, or erroneous du output. On installation, it dedicated 2.4GB to its root partition /dev/md0 and according to du -cx / is using less than 587192K of that space. Unfortunately, however, df says it's full. </div>
<div><div><br></div><div>bash-3.2# df -k</div><div>Filesystem 1K-blocks Used Available Use% Mounted on</div><div>rootfs 2451064 2425764 0 100% /</div><div>/dev/root 2451064 2425764 0 100% /</div>
</div><div><br></div><div><div>bash-3.2# mount</div><div>/dev/md0 on / type ext3 (rw,data=ordered)</div></div><div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>As a result, any number of apps from the stock firmware are prevented from running and those that do hobble along spam the logs to the point of uselessness w/complaints. The catch? I can't find a safe way to fsck it. Conventional shutdown commands to force a fsck aren't an option/are just plain missing on the box. Using tune2fs to set the check interval ridiculously low to force a check upon reboot similarly didn't work. Unfortunately, the ARM-based architecture also doesn't support booting to a removable USB device, knocking out the only other safe way I can think of to fsck it. Pop new firmware on to start from scratch? I'd love to at this point, but the firmware installation process requires 1024 megs of free disk space.</div>
<div><br></div><div>Thoughts? Any ideas on how to safely get it cleaned up and accurately reporting its free space while the root filesystem is live and booted?</div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
<br></div><div>-Sean</div>