|
Here's
my output:
# xfs_repair -n -r /dev/sda3 /dev/sda2 Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 0 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 4 - agno = 2 - agno = 10 - agno = 11 - agno = 9 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Best, J. On 12/22/2012 06:45 PM, Dave Chinner wrote: On Sat, Dec 22, 2012 at 11:10:24AM -0500, Jeffrey wrote:Ok, I tried running the command. Here's my output: # xfs_repair -n -r /dev/sda2 /dev/sda3 # Phase 1 - find and verify superblock... # bad primary superblock - bad magic number 111 # # attempting to find secondary superblock... # ................ and the dots are still just going after about 15 min. What should I do?Try pointing xfs_repair to the correct devices. From looking atthe earlier xfs_info output you posted, you've told it the realtime device is the data device and vice versa. i.e. you should be running: # xfs_repair -n -r /dev/sda3 /dev/sda2 Cheers, Dave. |
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
