From: Sander <sander@humilis.net>
To: Steve Freitas <sflist@ihonk.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs volume mounts and dies (was Re: Segfault in btrfsck)
Date: Thu, 7 Jan 2010 09:23:05 +0100 [thread overview]
Message-ID: <20100107082305.GA29892@cumulus> (raw)
In-Reply-To: <1262808695.6214.9.camel@phat>
Hello Steve,
Steve Freitas wrote (ao):
> Alright, I'll trash it and start over with a different drive.
With the danger of mentioning the obvious: you could do a few
destructive badblocks runs on that disk to see if SMART keeps adding up
to the bad blocks list.
With kind regards, Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2010-01-07 8:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 23:56 Segfault in btrfsck Steve Freitas
2010-01-03 22:57 ` btrfs volume mounts and dies (was Re: Segfault in btrfsck) Steve Freitas
2010-01-04 0:37 ` Steve Freitas
2010-01-05 22:55 ` Steve Freitas
2010-01-06 7:52 ` Sander
2010-01-06 15:59 ` Steve Freitas
2010-01-06 17:24 ` Johannes Hirte
2010-01-06 20:11 ` Steve Freitas
2010-01-07 8:23 ` Sander [this message]
2010-01-07 18:28 ` What protection does btrfs checksumming currently give? (Was Re: btrfs volume mounts and dies (was Re: Segfault in btrfsck)) Steve Freitas
2010-01-07 19:29 ` jim owens
2010-01-07 21:00 ` Johannes Hirte
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=20100107082305.GA29892@cumulus \
--to=sander@humilis.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sflist@ihonk.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 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.