http://oss.sgi.com/bugzilla/show_bug.cgi?id=396
t.j.pinkert@xxxxxxxxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority| |P1
Platform| |All
------- Additional Comments From t.j.pinkert@xxxxxxxxxxxxxxxxxx 2006-01-04
03:10 CST -------
(In reply to comment #0)
> Hi,
>
> After upgrading Linux kernel to 2.6.11-rc3 from 2.6.9, the XFS file system
> seems corrupted.
I installed a new system (Debian testing) with a kernel.org 2.6.14.5 kernel and
expereinced the same problems on my XFS filesystem. See previous message for the
things.
The behaviour came up first when deleting a directory with 'rm -r'. (when
running as root a complete bunch of kernelcode came along saying the memory is
not consistent with the fs. (are these normaly logged? logs are on a ext3 fs so
should be saved). In both cases i had to unmount (some forced message came
along) and remount, but this did not help. something strange in the rm output
was that there were // in the pathnames.
At that stage I unmounted and ran both xfs_check and a xfs_repair -n of which i
have the output saved in files (if this can help). The filesystem appeared to
have errors and thus was repaired with xfs_repair (whose output i did not save
unfortunately).
After this i lost a few directories to lost+found (fortunately i could backup
the most important stuff first as reading the fs appeared no problem). doing a
rm -r gave the 'Directory not empty' stuff.
Some extra information:
XFS runs on top of a striped logical volume.
Hope to help a bit with these. Until now i could not reproduce (and hope not to
do) the rm -r which crashes the fs kernel code.
Tjeerd Pinkert
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|