Re: 2nd Attempt - FSCK Errors

[Theodore Ts'o <tytso@mit.edu>]

On Fri, May 03, 2013 at 02:31:41PM +0100, Stephen Elliott wrote:
> Well... Funny enough, the device which I ran debugfs on was the other
> ReadyNAS device, not the one with the issue anyway. I wanted to test it
> first.

Was the inode number from the other device as well?  Sorry, this is
the first I've heard that there are two ReadyNAS devices in play.
It's one of the reasons why it's really painful to try to be a help
desk for these sorts of questions over e-mail....

> I suspect the underlying architecture supporting RAID in these devices
> screws with the debugfs interface.

Debugfs uses the standard Linux block device interface.  If that's not
sane, e2fsck isn't going to be sane either, and it's a kernel bug.  At
that point, you'll have to talk to ReadyNAS folks since they are
providing the kernel you are using (or the wonky non-standard
hardware, or both....)

> I just find it bizarre that I get the same message regarding multiply
> assigned blocks in 0 files on every FSCK as in it never gets resolved.
> But... No issues with file access or no bad logs etc. I do have a case open
> with Netgear support, since this is basically an appliance.

There have been NAS boxes out there which have used non-standard, out
of tree kernel patches that have resulted in their devices using
non-standard file system formats.  So that's yet another thing which
can't be ruled out...

						- Ted