Question about XFS recovery and error

Question about XFS recovery and error

[Mike Gao]

[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]

The USB key is mounted automatically at boot and no error report with XFS
recovery.
But when I did a file copy on a USB key which XFS filesystem could be
corrupted by some reason,
I got endless repeat of ERROR message printed on the screen.

Should XFS recovery this at the beginning when mounting?

[42949387.250000] Starting XFS recovery on filesystem: sda (logdev:
internal)
[42949387.330000] Ending XFS recovery on filesystem: sda (logdev: internal)
[42949388.600000] Starting XFS recovery on filesystem: sdb1 (logdev:
internal)
[42949388.640000] Ending XFS recovery on filesystem: sdb1 (logdev: internal)


cp /mnt/USB0disk1/iCarly-4.ts ./iCarly-4-10.ts

[ 3234.740000] Filesystem "sda": XFS internal error xfs_btree_check_sblock
at line 120 of file fs/xfs/xfs_btree.c.  Caller 0x8718e102
[ 3234.740000]
[ 3234.750000] regs can't be NULL.
[ 3234.760000] Filesystem "sda": page discard on page 876a1914, inode 0x91,
offset 91160576.
[ 3235.150000] Filesystem "sda": XFS internal error xfs_btree_check_sblock
at line 120 of file fs/xfs/xfs_btree.c.  Caller 0x8718e102

Thanks,
Mike

[-- Attachment #1.2: Type: text/html, Size: 1392 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Question about XFS recovery and error

[Michael Monnerie]

[-- Attachment #1.1: Type: Text/Plain, Size: 687 bytes --]

On Freitag, 20. August 2010 Mike Gao wrote:
> Should XFS recovery this at the beginning when mounting?
 
I've had this several times. XFS doesn't normally detect errors during 
mount, because it doesn't run fsck - no filesystem does that. So you'll 
trip over errors as you use the files involved - like this one.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Question about XFS recovery and error

[Eric Sandeen]

Mike Gao wrote:
> The USB key is mounted automatically at boot and no error report with
> XFS recovery.
> But when I did a file copy on a USB key which XFS filesystem could be
> corrupted by some reason,
> I got endless repeat of ERROR message printed on the screen. 
> 
> Should XFS recovery this at the beginning when mounting? 
> 
> [42949387.250000] Starting XFS recovery on filesystem: sda (logdev:
> internal)
> [42949387.330000] Ending XFS recovery on filesystem: sda (logdev: internal)
> [42949388.600000] Starting XFS recovery on filesystem: sdb1 (logdev:
> internal)
> [42949388.640000] Ending XFS recovery on filesystem: sdb1 (logdev: internal)
> 

first off, the above is an indication that you're not cleanly unmounting
the filesystem.

> cp /mnt/USB0disk1/iCarly-4.ts ./iCarly-4-10.ts
> 
> [ 3234.740000] Filesystem "sda": XFS internal error
> xfs_btree_check_sblock at line 120 of file fs/xfs/xfs_btree.c.  Caller
> 0x8718e102
> [ 3234.740000]
> [ 3234.750000] regs can't be NULL.
> [ 3234.760000] Filesystem "sda": page discard on page 876a1914, inode
> 0x91, offset 91160576.
> [ 3235.150000] Filesystem "sda": XFS internal error
> xfs_btree_check_sblock at line 120 of file fs/xfs/xfs_btree.c.  Caller
> 0x8718e102

This is probably a result of a write cache which isn't properly flushed
during use prior to unplug (i.e. barriers; no idea what usb keys have
for write caches etc, but btree errors wouldn't be unheard of due to
lost/reordered writes due to write cache failure)

As to your other question, Michael is right, filesystems don't call out
to userspace repair tools when they encounter an error like this.

You could make xfs_repair run prior to mount, but I'd focus more on
why you're getting a corrupted filesystem in the first place.

-Eric

> Thanks,
> Mike
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs