From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: fsck with "err is 1"
Date: 23 Nov 2011 19:32:00 +0100 [thread overview]
Message-ID: <ByQ7hQli1uB@helmut.hullen.de> (raw)
In-Reply-To: <4ECD3104.3050205@jan-o-sch.net>
Hallo, Jan,
Du meintest am 23.11.11:
>> One big problem of btrfs seems to be: you can't see on which
>> partition/ disk the defect sector (or something else) may be
> A recent kernel (3.2, still rc) will tell you the byte number when an
> error occurs, and also give the the opportunity to resolve this
> address to all files affected.
May be. I had used the brand new kernel 3.1.
btrfs may be fine when it works as proposed. It's still under heavy
construction.
I had to rebuild my 4-TByte archive the second time within 1 year -
that's no reliable system.
May be the situation for really big bundles of disk gets better when
something like raid 5 does work. I'll wait.
Viele Gruesse!
Helmut
prev parent reply other threads:[~2011-11-23 18: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
2011-11-23 17:44 ` Jan Schmidt
2011-11-23 18:32 ` Helmut Hullen [this message]
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=ByQ7hQli1uB@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