* mount: /dev/md0: can't read superblock
@ 2007-10-21 1:02 Greg Martyn
2007-10-21 23:27 ` David Chinner
2007-10-22 0:24 ` Eric Sandeen
0 siblings, 2 replies; 6+ messages in thread
From: Greg Martyn @ 2007-10-21 1:02 UTC (permalink / raw)
To: xfs
Hi all,
After running "xfs_fsr -v /home", I got a bunch of error messages
saying that certain files (/home/.[three letters that i forgot])
couldn't be removed. After that, my system stopped working properly,
so I restarted. Now:
[root@localhost ~]# mount /dev/md0 /home/
mount: /dev/md0: can't read superblock
uh oh.
md0 is a raid5 that /proc/mdstat reports as working properly.
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39
EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]# cat /etc/redhat-release
Fedora release 7 (Moonshine)
[root@localhost ~]# yum list xfsprogs xfsdump
Loading "changelog" plugin
Installed Packages
xfsdump.x86_64 2.2.45-2.fc7 installed
xfsprogs.i386 2.8.21-1.fc7 installed
xfsprogs.x86_64 2.8.21-1.fc7 installed
Any help is appreciated.
Thanks,
greg
Here's dmesg when I try to mount:
Filesystem "md0": Disabling barriers, not supported by the underlying device
XFS mounting filesystem md0
Starting XFS recovery on filesystem: md0 (logdev: internal)
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
fs/xfs/xfs_alloc.c. Caller 0xffffffff88a394a3
Call Trace:
[<ffffffff88a37943>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
[<ffffffff88a394a3>] :xfs:xfs_free_extent+0xa9/0xc9
[<ffffffff88a6b494>] :xfs:xlog_recover_process_efi+0xfc/0x12f
[<ffffffff88a6c833>] :xfs:xlog_recover_process_efis+0x4f/0x81
[<ffffffff88a6c87e>] :xfs:xlog_recover_finish+0x19/0x9a
[<ffffffff88a712ba>] :xfs:xfs_mountfs+0x830/0x94a
[<ffffffff810b68e2>] set_blocksize+0x8c/0x99
[<ffffffff88a770d8>] :xfs:xfs_mount+0x317/0x39d
[<ffffffff88a86e5e>] :xfs:xfs_fs_fill_super+0x0/0x1aa
[<ffffffff88a86edc>] :xfs:xfs_fs_fill_super+0x7e/0x1aa
[<ffffffff81248a41>] __down_write_nested+0x12/0x92
[<ffffffff810a7b18>] get_filesystem+0x12/0x35
[<ffffffff8109586b>] sget+0x37f/0x391
[<ffffffff810952a4>] set_bdev_super+0x0/0xf
[<ffffffff810952b3>] test_bdev_super+0x0/0xd
[<ffffffff810962a3>] get_sb_bdev+0x11d/0x16a
[<ffffffff81095c80>] vfs_kern_mount+0x93/0x11a
[<ffffffff81095d56>] do_kern_mount+0x43/0xdd
[<ffffffff810a993c>] do_mount+0x691/0x705
[<ffffffff81115824>] radix_tree_delete+0x1b4/0x1cc
[<ffffffff810a852f>] mntput_no_expire+0x1c/0x92
[<ffffffff8109d87d>] link_path_walk+0xce/0xe0
[<ffffffff810a5b77>] iput+0x42/0x7b
[<ffffffff8109db77>] do_path_lookup+0x1a3/0x21e
[<ffffffff8109c66e>] getname+0x14c/0x1b2
[<ffffffff81075eda>] zone_statistics+0x3f/0x60
[<ffffffff810708e0>] __alloc_pages+0x72/0x2d4
[<ffffffff810a9a3a>] sys_mount+0x8a/0xcd
[<ffffffff81009cd5>] tracesys+0xd5/0xda
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
fs/xfs/xfs_alloc.c. Caller 0xffffffff88a394a3
Call Trace:
[<ffffffff88a37943>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
[<ffffffff88a394a3>] :xfs:xfs_free_extent+0xa9/0xc9
[<ffffffff88a747d4>] :xfs:xfs_trans_log_efd_extent+0x1c/0x4b
[<ffffffff88a6b494>] :xfs:xlog_recover_process_efi+0xfc/0x12f
[<ffffffff88a6c833>] :xfs:xlog_recover_process_efis+0x4f/0x81
[<ffffffff88a6c87e>] :xfs:xlog_recover_finish+0x19/0x9a
[<ffffffff88a712ba>] :xfs:xfs_mountfs+0x830/0x94a
[<ffffffff810b68e2>] set_blocksize+0x8c/0x99
[<ffffffff88a770d8>] :xfs:xfs_mount+0x317/0x39d
[<ffffffff88a86e5e>] :xfs:xfs_fs_fill_super+0x0/0x1aa
[<ffffffff88a86edc>] :xfs:xfs_fs_fill_super+0x7e/0x1aa
[<ffffffff81248a41>] __down_write_nested+0x12/0x92
[<ffffffff810a7b18>] get_filesystem+0x12/0x35
[<ffffffff8109586b>] sget+0x37f/0x391
[<ffffffff810952a4>] set_bdev_super+0x0/0xf
[<ffffffff810952b3>] test_bdev_super+0x0/0xd
[<ffffffff810962a3>] get_sb_bdev+0x11d/0x16a
[<ffffffff81095c80>] vfs_kern_mount+0x93/0x11a
[<ffffffff81095d56>] do_kern_mount+0x43/0xdd
[<ffffffff810a993c>] do_mount+0x691/0x705
[<ffffffff81115824>] radix_tree_delete+0x1b4/0x1cc
[<ffffffff810a852f>] mntput_no_expire+0x1c/0x92
[<ffffffff8109d87d>] link_path_walk+0xce/0xe0
[<ffffffff810a5b77>] iput+0x42/0x7b
[<ffffffff8109db77>] do_path_lookup+0x1a3/0x21e
[<ffffffff8109c66e>] getname+0x14c/0x1b2
[<ffffffff81075eda>] zone_statistics+0x3f/0x60
[<ffffffff810708e0>] __alloc_pages+0x72/0x2d4
[<ffffffff810a9a3a>] sys_mount+0x8a/0xcd
[<ffffffff81009cd5>] tracesys+0xd5/0xda
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
fs/xfs/xfs_alloc.c. Caller 0xffffffff88a394a3
Call Trace:
[<ffffffff88a37943>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
[<ffffffff88a394a3>] :xfs:xfs_free_extent+0xa9/0xc9
[<ffffffff88a42857>] :xfs:xfs_bmap_finish+0xee/0x167
[<ffffffff88a61e40>] :xfs:xfs_itruncate_finish+0x1a0/0x2e5
[<ffffffff88a7c8b5>] :xfs:xfs_inactive+0x241/0x43f
[<ffffffff88a868c6>] :xfs:xfs_fs_clear_inode+0xa5/0xed
[<ffffffff810a6445>] clear_inode+0xdd/0x134
[<ffffffff810a6574>] generic_delete_inode+0xd8/0x136
[<ffffffff88a6c433>] :xfs:xlog_recover_process_iunlinks+0x1d1/0x2f2
[<ffffffff88a6c89e>] :xfs:xlog_recover_finish+0x39/0x9a
[<ffffffff88a712ba>] :xfs:xfs_mountfs+0x830/0x94a
[<ffffffff810b68e2>] set_blocksize+0x8c/0x99
[<ffffffff88a770d8>] :xfs:xfs_mount+0x317/0x39d
[<ffffffff88a86e5e>] :xfs:xfs_fs_fill_super+0x0/0x1aa
[<ffffffff88a86edc>] :xfs:xfs_fs_fill_super+0x7e/0x1aa
[<ffffffff81248a41>] __down_write_nested+0x12/0x92
[<ffffffff810a7b18>] get_filesystem+0x12/0x35
[<ffffffff8109586b>] sget+0x37f/0x391
[<ffffffff810952a4>] set_bdev_super+0x0/0xf
[<ffffffff810952b3>] test_bdev_super+0x0/0xd
[<ffffffff810962a3>] get_sb_bdev+0x11d/0x16a
[<ffffffff81095c80>] vfs_kern_mount+0x93/0x11a
[<ffffffff81095d56>] do_kern_mount+0x43/0xdd
[<ffffffff810a993c>] do_mount+0x691/0x705
[<ffffffff81115824>] radix_tree_delete+0x1b4/0x1cc
[<ffffffff810a852f>] mntput_no_expire+0x1c/0x92
[<ffffffff8109d87d>] link_path_walk+0xce/0xe0
[<ffffffff810a5b77>] iput+0x42/0x7b
[<ffffffff8109db77>] do_path_lookup+0x1a3/0x21e
[<ffffffff8109c66e>] getname+0x14c/0x1b2
[<ffffffff81075eda>] zone_statistics+0x3f/0x60
[<ffffffff810708e0>] __alloc_pages+0x72/0x2d4
[<ffffffff810a9a3a>] sys_mount+0x8a/0xcd
[<ffffffff81009cd5>] tracesys+0xd5/0xda
xfs_force_shutdown(md0,0x8) called from line 4258 of file
fs/xfs/xfs_bmap.c. Return address = 0xffffffff88a42894
Filesystem "md0": Corruption of in-memory data detected. Shutting
down filesystem: md0
Please umount the filesystem, and rectify the problem(s)
Ending XFS recovery on filesystem: md0 (logdev: internal)
SELinux: (dev md0, type xfs) getxattr errno 5
xfs_force_shutdown(md0,0x1) called from line 423 of file
fs/xfs/xfs_rw.c. Return address = 0xffffffff88a7d715
xfs_force_shutdown(md0,0x1) called from line 423 of file
fs/xfs/xfs_rw.c. Return address = 0xffffffff88a7d715
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: mount: /dev/md0: can't read superblock
2007-10-21 1:02 mount: /dev/md0: can't read superblock Greg Martyn
@ 2007-10-21 23:27 ` David Chinner
2007-10-22 0:24 ` Eric Sandeen
1 sibling, 0 replies; 6+ messages in thread
From: David Chinner @ 2007-10-21 23:27 UTC (permalink / raw)
To: Greg Martyn; +Cc: xfs
On Sat, Oct 20, 2007 at 09:02:14PM -0400, Greg Martyn wrote:
> Hi all,
> After running "xfs_fsr -v /home", I got a bunch of error messages
> saying that certain files (/home/.[three letters that i forgot])
> couldn't be removed. After that, my system stopped working properly,
> so I restarted. Now:
A corrupted freespace btree, by the look of it.
What errors occurred you syslog when the system started playing
up? I/O errors? Corruption errors?
xfs_repair will probably be the only thing you can do here to correct
the problem....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: mount: /dev/md0: can't read superblock
2007-10-21 1:02 mount: /dev/md0: can't read superblock Greg Martyn
2007-10-21 23:27 ` David Chinner
@ 2007-10-22 0:24 ` Eric Sandeen
2007-10-22 0:52 ` David Chinner
1 sibling, 1 reply; 6+ messages in thread
From: Eric Sandeen @ 2007-10-22 0:24 UTC (permalink / raw)
To: Greg Martyn; +Cc: xfs
Greg Martyn wrote:
> Hi all,
> After running "xfs_fsr -v /home", I got a bunch of error messages
> saying that certain files (/home/.[three letters that i forgot])
> couldn't be removed. After that, my system stopped working properly,
> so I restarted. Now:
>
> [root@localhost ~]# mount /dev/md0 /home/
> mount: /dev/md0: can't read superblock
>
> uh oh.
dmesg says it's corrupted.
You should probably run repair on it. But being raid, if something went
wrong w/ the raid, that could make it worse... run xfs_repair -n and see
what it *would* fix.
-Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: mount: /dev/md0: can't read superblock
2007-10-22 0:24 ` Eric Sandeen
@ 2007-10-22 0:52 ` David Chinner
2007-10-22 3:47 ` Greg Martyn
0 siblings, 1 reply; 6+ messages in thread
From: David Chinner @ 2007-10-22 0:52 UTC (permalink / raw)
To: Eric Sandeen; +Cc: Greg Martyn, xfs
On Sun, Oct 21, 2007 at 07:24:45PM -0500, Eric Sandeen wrote:
> Greg Martyn wrote:
> > Hi all,
> > After running "xfs_fsr -v /home", I got a bunch of error messages
> > saying that certain files (/home/.[three letters that i forgot])
> > couldn't be removed. After that, my system stopped working properly,
> > so I restarted. Now:
> >
> > [root@localhost ~]# mount /dev/md0 /home/
> > mount: /dev/md0: can't read superblock
> >
> > uh oh.
>
> dmesg says it's corrupted.
>
> You should probably run repair on it. But being raid, if something went
> wrong w/ the raid, that could make it worse... run xfs_repair -n and see
> what it *would* fix.
xfs_repair does not check everything in the filesystem - some things it
simply rebuilds - like the free space btrees. you want to run xfs_check
to determine if the free space btrees are corrupt on disk or not.... ;)
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: mount: /dev/md0: can't read superblock
2007-10-22 0:52 ` David Chinner
@ 2007-10-22 3:47 ` Greg Martyn
2007-10-22 11:16 ` Justin Piszcz
0 siblings, 1 reply; 6+ messages in thread
From: Greg Martyn @ 2007-10-22 3:47 UTC (permalink / raw)
To: David Chinner; +Cc: Eric Sandeen, xfs
Thank you Eric and David. xfs_repair repaired the filesystem. I forgot
to save the output of xfs_fsr (in case you were curious about what
went wrong), but everything seems to be working fine again.
I just won't be defragging again any time soon ;-)
Thanks,
greg
On 10/21/07, David Chinner <dgc@sgi.com> wrote:
> On Sun, Oct 21, 2007 at 07:24:45PM -0500, Eric Sandeen wrote:
> > Greg Martyn wrote:
> > > Hi all,
> > > After running "xfs_fsr -v /home", I got a bunch of error messages
> > > saying that certain files (/home/.[three letters that i forgot])
> > > couldn't be removed. After that, my system stopped working properly,
> > > so I restarted. Now:
> > >
> > > [root@localhost ~]# mount /dev/md0 /home/
> > > mount: /dev/md0: can't read superblock
> > >
> > > uh oh.
> >
> > dmesg says it's corrupted.
> >
> > You should probably run repair on it. But being raid, if something went
> > wrong w/ the raid, that could make it worse... run xfs_repair -n and see
> > what it *would* fix.
>
> xfs_repair does not check everything in the filesystem - some things it
> simply rebuilds - like the free space btrees. you want to run xfs_check
> to determine if the free space btrees are corrupt on disk or not.... ;)
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: mount: /dev/md0: can't read superblock
2007-10-22 3:47 ` Greg Martyn
@ 2007-10-22 11:16 ` Justin Piszcz
0 siblings, 0 replies; 6+ messages in thread
From: Justin Piszcz @ 2007-10-22 11:16 UTC (permalink / raw)
To: Greg Martyn; +Cc: David Chinner, Eric Sandeen, xfs
I degragment many arrays (sw raid) and single disks without any problems,
not sure what your issue was.
On Sun, 21 Oct 2007, Greg Martyn wrote:
> Thank you Eric and David. xfs_repair repaired the filesystem. I forgot
> to save the output of xfs_fsr (in case you were curious about what
> went wrong), but everything seems to be working fine again.
>
> I just won't be defragging again any time soon ;-)
>
> Thanks,
> greg
>
> On 10/21/07, David Chinner <dgc@sgi.com> wrote:
>> On Sun, Oct 21, 2007 at 07:24:45PM -0500, Eric Sandeen wrote:
>>> Greg Martyn wrote:
>>>> Hi all,
>>>> After running "xfs_fsr -v /home", I got a bunch of error messages
>>>> saying that certain files (/home/.[three letters that i forgot])
>>>> couldn't be removed. After that, my system stopped working properly,
>>>> so I restarted. Now:
>>>>
>>>> [root@localhost ~]# mount /dev/md0 /home/
>>>> mount: /dev/md0: can't read superblock
>>>>
>>>> uh oh.
>>>
>>> dmesg says it's corrupted.
>>>
>>> You should probably run repair on it. But being raid, if something went
>>> wrong w/ the raid, that could make it worse... run xfs_repair -n and see
>>> what it *would* fix.
>>
>> xfs_repair does not check everything in the filesystem - some things it
>> simply rebuilds - like the free space btrees. you want to run xfs_check
>> to determine if the free space btrees are corrupt on disk or not.... ;)
>>
>> Cheers,
>>
>> Dave.
>> --
>> Dave Chinner
>> Principal Engineer
>> SGI Australian Software Group
>>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-10-22 11:16 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-21 1:02 mount: /dev/md0: can't read superblock Greg Martyn
2007-10-21 23:27 ` David Chinner
2007-10-22 0:24 ` Eric Sandeen
2007-10-22 0:52 ` David Chinner
2007-10-22 3:47 ` Greg Martyn
2007-10-22 11:16 ` Justin Piszcz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox