public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 6 Jan 2010 08:52:53 +0100	[thread overview]
Message-ID: <20100106075253.GA5665@cumulus> (raw)
In-Reply-To: <1262732153.4509.1.camel@phat>

Hello Steve,

Steve Freitas wrote (ao):
> Should I take it by the lack of list response that I should just flush
> this partition down the toilet and start over? Or is everybody either
> flummoxed or on vacation?

I don't have your original mail, but I think I remember you mentioned a
lot of bad sectors on that disk reported by SMART.

If that is indeed the case it might be dificult for the people who might
be able to help you, to help you.

Please ignore me if I confused your mail with another.

	With kind regard, Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  reply	other threads:[~2010-01-06  7:52 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 [this message]
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
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=20100106075253.GA5665@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox