From: martin f krafft <madduck@madduck.net>
To: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: catch22: xfs_repair fails, tells me to mount, which fails
Date: Wed, 30 Aug 2006 16:15:48 +0200 [thread overview]
Message-ID: <20060830141548.GA21325@piper.madduck.net> (raw)
In-Reply-To: <44F597F9.6020803@agami.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
also sprach Shailendra Tripathi <stripathi@agami.com> [2006.08.30.1551 +0200]:
> By any chance, did you saw any disk I/O error ?
No, definitely not.
> If there is no disk I/O error scenario, following information
> would be more useful.
>
> 1. /usr/sbin/xfs_logprint -s 0 -D <device>
> 2. /usr/sbin/xfs_logprint -d <device>
Thanks for the info. I managed to restore the filesystem with
xfs_repair -L in the mean time (see followup post), but this is what
I'll keep in mind for the next time.
Btw: there's the xfs and linux-xfs mailing list, and I am confused
about whether they're separate or merged, and which one I should be
using. If you have any input, I'd love to hear it.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
no micro$oft components were used
in the creation or posting of this email.
therefore, it is 100% virus free
and does not use html by default (yuck!).
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-30 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 8:24 catch22: xfs_repair fails, tells me to mount, which fails martin f krafft
2006-08-30 11:41 ` martin f krafft
2006-08-30 13:51 ` Shailendra Tripathi
2006-08-30 14:15 ` martin f krafft [this message]
2006-08-30 19:15 ` Eric Sandeen
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=20060830141548.GA21325@piper.madduck.net \
--to=madduck@madduck.net \
--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