Hello,
I had a problem with the xfs_repair program, and seen the same in the mailing
list archive. Here are the headers of this message :
To: linux-xfs@xxxxxxxxxxx
Subject: xfs_repair problem
From: Benito Venegas <venevene@xxxxxxxxxxxxxx>
Date: Thu, 14 Mar 2002 11:55:14 -0500
URL : http://oss.sgi.com/projects/xfs/mail_archive/200203/msg00277.html
If the problem have been fixed in CVS or in xfs_repair > 2.0.3, please ignore
my message. (there was no valuable data on my system)
after a power faillure when my PC was booting, my xfs 1.1 partition on my
gentoo 1.2 i686 system get corrupted. after that, when I tryed to list or use
the /etc directory, this crash the system without any message or log.
When I tried to use xfs_repair, it leads to a "Fatal error". After the fisrt
xfs_repair, a few error have been fixed, but it stop with a fatal error, and
my /etc directory have disapeard. Here is the output when I rerun xfs_repair
now :
# xfs_repair /dev/hda3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- clearing existing "lost+found" inode
- marking entry "lost+found" to be deleted
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- ensuring existence of lost+found directory
- traversing filesystem starting at / ...
rebuilding directory inode 128
- traversal finished ...
- traversing all unattached subtrees ...
fatal error -- can't read block 0 for directory inode 16909320
In the "Benito Venegas" message, you say that xfs_repair is probably runing
out of memory. I have 256Mb of physical ram, and 256Mb of swap. Isn't that
enough ? (my xfs partition is about 4.4 Gb, 97% used).
thanks, and I hope this will help to correct the bug if there is one.
--
Stéphane Poinsart (sart@xxxxxxx)
http://www.sart.host.sk
|