Re: Possible ext4 corruption - ACL related?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mar 11, 2009  12:18 +1030, Kevin Shanahan wrote:
> On Wed, 2009-03-11 at 12:13 +1030, Kevin Shanahan wrote:
> > 
> >   getfattr: apps/Gestalt.Net/SetupCD/program\040files/Business\040Objects/Common/3.5/bin/RptControllers.dll: Input/output error
> > 
> > And syslog shows:
> >   Mar 11 00:06:24 hermes kernel: attempt to access beyond end of device
> >   Mar 11 00:06:24 hermes kernel: dm-0: rw=0, want=946232834916360, limit=2147483648
> > 
> > hermes:~# debugfs /dev/dm-0
> > debugfs 1.41.3 (12-Oct-2008)
> > debugfs:  stat "local/apps/Gestalt.Net/SetupCD/program files/Business Objects/Common/3.5/bin/RptControllers.dll"
> > 
> > Inode: 875   Type: FIFO    Mode:  0611   Flags: 0xb3b9c185
> > Generation: 3690868    Version: 0x9d36b10d
> > User: 868313917   Group: -1340283792   Size: 0
> > File ACL: 0    Directory ACL: 0
> > Links: 1   Blockcount: 0
> > Fragment:  Address: 0    Number: 0    Size: 0
> > ctime: 0x0742afc4 -- Sun Nov 11 06:51:24 1973
> > atime: 0x472a2311 -- Fri Nov  2 05:33:45 2007
> > mtime: 0x80c59881 -- Fri Jun 18 09:51:21 2038
> > Size of extra inode fields: 4
> > BLOCKS:

There isn't anything obvious here that would imply reading a wacky block
beyond the end of the filesystem.  I even checked if e.g. you had quotas
enabled and the bogus UID/GID would result in the quota file becoming
astronomically large or something, but the numbers don't seem to match.

There are no blocks in the file, no xattr block ("File ACL" should be
renamed...).

> hermes:~# ls -l /srv/samba/local/apps/Gestalt.Net/SetupCD/program\ files/Business\ Objects/Common/3.5/bin/RptControllers.dll 
> prwS--x--t 1 868313917 2954683504 0 1902-05-13 03:23 /srv/samba/local/apps/Gestalt.Net/SetupCD/program files/Business Objects/Common/3.5/bin/RptControllers.dll
> 
> I guess this is what Andreas meant by "turning a pile of manure into
> neatly organized fertilizer" :)

Yes, you should just delete the inodes reported corrupted in your
earlier postings in the 87x range - they contain nothing of value
anymore, and I suspect your troubles would be gone.  At least we
wouldn't be left wondering if you are seeing new corruption in
the same range of blocks, or just leftover badness.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux