> dmesg will tell you the real error.
I feel silly...dmesg does indeed say quite a bit...sample output at
the bottom of this message...I got quite a number of these, presumably
one each time xfs gave me an error.
> How did the filesystem go bad in the first place? What prompted
> the repair?
The repair was prompted by not being able to mount it. The corruption
was due to a heinous system crash when trying to do a pvmove on a lvm
volume group that this partitition was not on.
Thanks for your help
-Tupshin
dmesg output (let me know if I can give you any more info about this):
xfs_da_do_buf: bno 8388608
dir: inode 54540222
Filesystem "loop0": XFS internal error xfs_da_do_buf(1) at line 2176
of file fs/xfs/xfs_da_btree.c. Caller 0xc024a4
97
[<c024a229>] xfs_da_do_buf+0x749/0x900
[<c024a497>] xfs_da_read_buf+0x57/0x60
[<c038ce00>] ip_rcv_finish+0x0/0x280
[<c0373ef8>] netif_receive_skb+0x1b8/0x260
[<c03e85ce>] schedule+0x28e/0x490
[<c024a497>] xfs_da_read_buf+0x57/0x60
[<c0248210>] xfs_da_node_lookup_int+0x80/0x370
[<c0248210>] xfs_da_node_lookup_int+0x80/0x370
[<c025509f>] xfs_dir2_node_lookup+0x3f/0xc0
[<c024c70a>] xfs_dir2_lookup+0x12a/0x140
[<c027e27c>] xfs_dir_lookup_int+0x4c/0x130
[<c0283a70>] xfs_lookup+0x50/0x90
[<c02903f7>] linvfs_lookup+0x67/0xa0
[<c0165bdf>] real_lookup+0xcf/0x100
[<c0165e86>] do_lookup+0x96/0xb0
[<c0166573>] link_path_walk+0x6d3/0xda0
[<c02d2eb3>] tty_default_put_char+0x33/0x40
[<c02d3759>] opost+0x99/0x1b0
[<c0117f5f>] recalc_task_prio+0x8f/0x190
[<c0166ec3>] path_lookup+0x83/0x180
[<c0167189>] __user_walk+0x49/0x80
[<c0161b9c>] vfs_lstat+0x1c/0x60
[<c036e3b4>] kfree_skbmem+0x24/0x30
[<c036e471>] __kfree_skb+0xb1/0x140
[<c01622cb>] sys_lstat64+0x1b/0x40
[<c011fc7d>] __do_softirq+0x7d/0x80
[<c010876d>] do_IRQ+0xfd/0x130
[<c0106107>] syscall_call+0x7/0xb
|