From: Federico Sevilla III <jijo@fs3.ph>
To: XFS Mailing List <xfs@oss.sgi.com>
Subject: Mount Failure: Totally Zeroed Log
Date: Fri, 18 May 2007 14:08:25 +0800 [thread overview]
Message-ID: <20070518060825.GD3340@fs3.ph> (raw)
Hi,
I encountered the following error after an unclean shutdown:
Filesystem "md1": Disabling barriers, not supported by the underlying device
XFS mounting filesystem md1
XFS: totally zeroed log
Starting XFS recovery on filesystem: md1 (logdev: internal)
Filesystem "md1": XFS internal error xlog_valid_rec_header(1) at line 3503 of file fs/xfs/xfs_log_recover.c. Caller 0xf8992fbd
[<f8992a5d>] xlog_valid_rec_header+0xc5/0xd5 [xfs]
[<f8992fbd>] xlog_do_recovery_pass+0x550/0x90f [xfs]
[<f8992fbd>] xlog_do_recovery_pass+0x550/0x90f [xfs]
[<f89933c1>] xlog_do_log_recovery+0x45/0xa6 [xfs]
[<f899343f>] xlog_do_recover+0x1d/0x102 [xfs]
[<f89935ab>] xlog_recover+0x87/0x98 [xfs]
[<f898c4bd>] xfs_log_mount+0x8d/0xce [xfs]
[<f8994c17>] xfs_mountfs+0x982/0xc63 [xfs]
[<f89888ee>] xfs_ioinit+0x21/0x26 [xfs]
[<f899b3c6>] xfs_mount+0x30b/0x37e [xfs]
[<f89abf24>] vfs_mount+0x28/0x2c [xfs]
[<f89abdb5>] xfs_fs_fill_super+0x6e/0x193 [xfs]
[<c019dbd2>] snprintf+0x16/0x1a
[<c017a1cd>] disk_name+0x25/0x66
[<c0151c10>] get_sb_bdev+0xca/0x117
[<c0158146>] __link_path_walk+0xadd/0xbd2
[<f89abef8>] xfs_fs_get_sb+0x1e/0x22 [xfs]
[<f89abd47>] xfs_fs_fill_super+0x0/0x193 [xfs]
[<c0151de6>] vfs_kern_mount+0x35/0x66
[<c0151e40>] do_kern_mount+0x29/0x39
[<c0163ffd>] do_new_mount+0x67/0xa4
[<c01645f9>] do_mount+0x153/0x16b
[<c0164459>] copy_mount_options+0x4c/0x99
[<c016489d>] sys_mount+0x79/0xba
[<c010278b>] syscall_call+0x7/0xb
XFS: log mount/recovery failed: error 117
XFS: log mount failed
The machine runs Debian GNU/Linux 4.0 (Etch), with a custom-built 2.6.18
kernel using the Debian 2.6.18 source and the OpenVZ patch. xfs_repair
is able to repair the filesystem, but most of the files just end up in
lost+found. I have verified that write cache on both drives has been
disabled, and hdparm is set to disable them everytime during startup.
Any clues as to what could be causing this?
Thank you very much.
Cheers!
--
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph
next reply other threads:[~2007-05-18 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 6:08 Federico Sevilla III [this message]
2007-05-21 7:26 ` Mount Failure: Totally Zeroed Log Timothy Shimmin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070518060825.GD3340@fs3.ph \
--to=jijo@fs3.ph \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox