On Thu, 2008-02-14 at 22:42 +1100, Russell Coker wrote: > Package: xfsprogs > Version: 2.8.11-1 > Severity: critical > Justification: breaks the whole system
Heh, er, just a tad extreme? (its not clear how an xfs_check SEGV can "break the whole system"...?) > I have a filesystem which causes a SEGV when I try to check it. > > The problem started when I unexpectedly powered the machine down causing some > data loss. When I booted it up again the kernel gave errors about corrupted > data structures (which I unfortunately didn't make a note of). Now when I > try to check it (on another machine) it gives the following. > > NB The filesystem has no secret data, I would be happy to give you a copy, I > could put it on a machine on the net that you can access or give you an IDE > disk with a copy if you are in Melbourne. Could you run xfs_metadump(8) on the device, put it somewhere that it can be downloaded, and send this mail to [EMAIL PROTECTED] (I can do that for you if you prefer the Debian bug tracking system), and someone will take a look at it from SGI. > /usr/sbin/xfs_check: line 28: 9686 Segmentation fault xfs_db$DBOPTS -i > -p xfs_check -c "check$OPTS" $1 Also, if you could run the above xfs_db inside gdb, and get a stack trace (bt), that would also help. BTW, another (better) option to xfs_check is to run "xfs_repair -n", which will also give you a rundown on whats needed to fix your filesystem. If it all looks bearable, run without -n to proceed with the repair. cheers. -- Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
