From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: fsck with "err is 1"
Date: 23 Nov 2011 18:32:00 +0100 [thread overview]
Message-ID: <ByQ7Wl$y1uB@helmut.hullen.de> (raw)
In-Reply-To: <5ED58F1E-368C-414F-BA60-9C8E240338F6@orcaware.com>
Hallo, Blair,
Du meintest am 23.11.11:
>> I can't answer that, but I can tell you that fsck for btrfs right
>> now is almost useless. It can't fix anyting.
> Thank you, I've read that fsck doesn't fix anything. I was curious
> if doing the scrub would resolve it.
I had tried ... about 4 Tbyte data have gone.
3 disks bundled with data=raid0, metadata=raid1.
One disk had problems, before I run "scrub" I could read most files,
Running "scrub": all had gone.
One big problem of btrfs seems to be: you can't see on which partition/
disk the defect sector (or something else) may be, if there is 1 error
in 1 partition you have to restore the complete bundle of disks/
partitions.
Yes - I know: btrfs is still under construction.
In my special case: the 4 TByte are a kind of video archive. No
"valuable" data, only "nice to have". And old people still know the
behaviour of old 35 mm film and/or VHS cassettes: they have errors. But
these errors don't damage the whole archive.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-11-23 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 5:33 fsck with "err is 1" Blair Zajac
2011-11-23 6:02 ` Fajar A. Nugraha
2011-11-23 16:48 ` Blair Zajac
2011-11-23 17:32 ` Helmut Hullen [this message]
2011-11-23 17:44 ` Jan Schmidt
2011-11-23 18:32 ` Helmut Hullen
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='ByQ7Wl$y1uB@helmut.hullen.de' \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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