All of lore.kernel.org
 help / color / mirror / Atom feed
From: evan d <forumscollective@gmail.com>
To: quwenruo.btrfs@gmx.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Two partitionless BTRFS drives no longer seen as containing BTRFS filesystem
Date: Sun, 7 Oct 2018 14:25:54 +0200	[thread overview]
Message-ID: <CAG__1a7yz1iX7+M7ybGNVHLiZehactYiiJ6EbnA57RDzzx=V2Q@mail.gmail.com> (raw)
In-Reply-To: <8968c012-7732-2338-c505-2027539cbe56@gmx.com>

> > I may as well use wipefs to clear crud from both drives, partition and
> > format them and then use them elsewhere.   -- this more or less
> > accurately summarise the situation?
>
> Unfortunately, yes.


I recall the machine these drives were in lost the onboard NIC when
the desktop switch it was connected to went up in smoke.  Perhaps it
was at that point the corruption occurred, albeit I seem to recall
checking the drives at the time.  Such is life.  If they pass extended
SMART tests they'll go back into use.

  reply	other threads:[~2018-10-07 12:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 23:23 Two partitionless BTRFS drives no longer seen as containing BTRFS filesystem evan d
2018-10-07  0:32 ` Remi Gauvin
2018-10-07  6:08   ` evan d
2018-10-07  0:41 ` Qu Wenruo
2018-10-07  6:10   ` evan d
2018-10-07  6:26     ` Qu Wenruo
2018-10-07  6:47       ` evan d
2018-10-07  7:39         ` Qu Wenruo
2018-10-07  8:09           ` evan d
2018-10-07  8:19             ` Qu Wenruo
2018-10-07  8:28               ` evan d
2018-10-07  9:47                 ` Qu Wenruo
2018-10-07 10:39                   ` evan d
2018-10-07 10:51                     ` Qu Wenruo
2018-10-07 12:25                       ` evan d [this message]
2018-10-07 12:26                         ` evan d

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='CAG__1a7yz1iX7+M7ybGNVHLiZehactYiiJ6EbnA57RDzzx=V2Q@mail.gmail.com' \
    --to=forumscollective@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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.