The question is "Is there anything else we can do except print these message?
For example, call a recovery function which already be implemented in user tools to fix it.
I ask this because if the disk is in customer's side, they may not be able to format it.
Thanks,
Mike
------------------------------
Message: 2
Date: Thu, 19 Aug 2010 17:32:33 -0500
From: Mike Gao <ygao.linux@xxxxxxxxx>
Subject: Question about XFS recovery and error
To: xfs@xxxxxxxxxxx
Message-ID:
<AANLkTi=prcC7ky3ikNTJ+py8XnALGf4THSOCUwqYhxaq@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20100819/62574c74/attachment.html>
------------------------------
End of xfs Digest, Vol 24, Issue 44
***********************************
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
