From: Timo Nentwig <btrfs@nentwig.biz>
To: linux-btrfs@vger.kernel.org
Subject: Re: can't read superblock (but could mount)
Date: Tue, 14 Feb 2012 19:54:43 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1202141950420.18337@localhost> (raw)
In-Reply-To: <20120214184131.GZ1573@shiny>
On Tue, 14 Feb 2012, Chris Mason wrote:
> As for how we got here, I think you said you were originally running
> something older than 3.2 when these problems started, correct?
Nope, I was already on 3.2.1 or 3.2.4. I restored a backup in the meantime
and already had to soft-reset the box:
# ls -ltr ~/.kde4/share/config/
ls: reading directory /home/foo/.kde4/share/config/: Input/output error
Sigh...
next prev parent reply other threads:[~2012-02-14 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 19:30 can't read superblock (but could mount) btrfs
2012-02-10 22:18 ` Chris Mason
2012-02-10 23:39 ` Chris Mason
2012-02-11 6:27 ` btrfs
2012-02-13 13:09 ` Chris Mason
2012-02-14 17:37 ` Timo Nentwig
2012-02-14 18:41 ` Chris Mason
2012-02-14 18:54 ` Timo Nentwig [this message]
2012-02-14 21:14 ` Chris Mason
2012-02-15 6:03 ` Timo Nentwig
2012-02-15 13:23 ` Chris Mason
2012-02-16 17:04 ` Timo Nentwig
2012-02-16 18:14 ` Chris Mason
2012-02-17 3:35 ` Timo Nentwig
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=alpine.LNX.2.00.1202141950420.18337@localhost \
--to=btrfs@nentwig.biz \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.