From: Eric Sandeen <sandeen@sgi.com>
To: David Greaves <david@dgreaves.com>
Cc: linux-xfs@oss.sgi.com,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
nathans@sgi.com
Subject: Re: testing 2.6.14-rc4: unmountable fs after xfs_force_shutdown
Date: Sat, 25 Feb 2006 19:23:54 -0600 [thread overview]
Message-ID: <4401032A.10406@sgi.com> (raw)
In-Reply-To: <4400C94A.7070001@dgreaves.com>
David Greaves wrote:
> haze:~# mount /scratch
> mount: /dev/video_vg/video_lv: can't read superblock
>
> haze:~# xfs_repair -n /dev/video_vg/video_lv
> Phase 1 - find and verify superblock...
> superblock read failed, offset 0, size 524288, ag 0, rval 0
First, why can't it be read? any kernel messages as a result? can you
do a simple dd -from- this block device?
-Eric
next prev parent reply other threads:[~2006-02-26 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 21:16 testing 2.6.14-rc4: unmountable fs after xfs_force_shutdown David Greaves
2006-02-26 1:23 ` Eric Sandeen [this message]
2006-02-26 9:44 ` Odd LVM behaviour - was " David Greaves
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=4401032A.10406@sgi.com \
--to=sandeen@sgi.com \
--cc=david@dgreaves.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@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;
as well as URLs for NNTP newsgroup(s).