Synology & Fsck

[Jack]

I would personally go to runlevel 1, unmount the disk and run fsck on it and fix the problems. Then once you have a clean disk you should know if more investigation is required. Right now you have a borked filesystem and you shouldn't be running anything pn it until it's fixed. But that's just my opinion. 

Also, curious to how you set up the file system. What size blocks is it using? If your filesystem is going to have lots of small files, you are better off using a small lock size. Sometimes the default settings on creating filesystems are ok, but sometimes you want to tweak the settings for better use of the disk. A smaller disk with a lot of small files will benefit from optimizing the inode block-size. Although it looks like you have plenty of free inodes. Conversely if you have mostly big files, then using a bigger size block will improve system performance. Of course, this is irrelevant now, without wiping out the data on the drive.

Jack

--- On Wed, 6/2/10, Sean Crago <cragos at gmail.com> wrote:

From: Sean Crago <cragos at gmail.com>
Subject: Re: Synology & Fsck
To: "KCLUG" <kclug at kclug.org>
Date: Wednesday, June 2, 2010, 6:05 PM

Kelsay:
Very nearly all space in use is being used by the OS proper and, strangely, far less than required for an install. I could hose the system with an rm -rf / and still not have enough space to install new firmware, due to this phantom disk usage problem.


Andrew: 
I'm assuming md0 is on one or more of my two disks, but still investigating whether this is safe to do. Researching mdadm-style software RAID is top of my list of things to do in 9-10 hours after work, but not comfortable popping it out just yet/not sure how to tell if this /dev/md0 device is only on one of my disks and not on both, or a third device/onboard flash.


Jack:
Sorry about that - I did have the "fsck -n" output, but didn't want to make my post that much longer. Dumped it here, as well as "df -i" and "du -sxk /" output. The fsck does give multiple free space errors, and df -i only shows 13% of inodes in use.


http://docs.google.com/View?id=dgrxhrtx_82fmxvtsfg

Is there a way to safely fix the problem on a live filesystem, due to Synology's custom distro ignoring tune2fs's check interval settings on boot?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kclug.org/pipermail/kclug/attachments/20100603/fee8296a/attachment.htm>