From: Mck <mick@wever.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: corruption. notreelog has no effect? anything else to try?
Date: Sun, 17 Jul 2011 00:28:20 +0000 [thread overview]
Message-ID: <1310862500.6144.4.camel@localhost> (raw)
In-Reply-To: <CAG1y0sc-D1-5zkgsovtZG6emOc78GoZ64gQ1Lhufm=6Z3huEAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
> does btrfsck -s1 complete without error?
> If yes, you can try btrfs-select-super.
> [snip]
> if there's something mentioning "log", I'd try btrfs-zero-log first.
`btrfsck -s1 /dev/sda4` gave errors too.
So i skipped to running btrfs-zero-log. It ran without errors.
But running btrfsck again still gave the same errors.
So i went back and tried btrfs-select-super...
# ./btrfs-select-super -s1 /dev/sda4
using SB copy 1, bytenr 67108864
After this i tried mounting and it worked for all subvolumes!
I am ever so grateful for your help Fajar.
Unfortunately I didn't try mounting after the btrfs-zero-log so i don't
know if it or btrfs-select-super was actually the cure.
Knowing very little about zero-log and select-super should i continue
using my laptop like normal now?
Or is this filesystem still considered corrupt and i should backup and
format it all from scratch?
~mck
--
“Don’t worry about people stealing your ideas. If your ideas are any
good, you’ll have to ram them down people’s throats.” - Howard Aiken
| http://semb.wever.org | http://sesat.no
| http://tech.finn.no | Java XSS Filter
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-07-17 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 20:51 corruption. notreelog has no effect? anything else to try? mck
2011-07-15 22:19 ` Fajar A. Nugraha
2011-07-17 0:28 ` Mck [this message]
2011-07-17 0:26 ` Fajar A. Nugraha
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=1310862500.6144.4.camel@localhost \
--to=mick@wever.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox