From: "Justin" <yoosty69@netzero.com>
To: chris.mason@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs Bug?
Date: Thu, 8 Apr 2010 18:46:40 GMT [thread overview]
Message-ID: <20100408.114640.18413.0@webmail01.vgs.untd.com> (raw)
Unfortunately I did reformat.
Actually, I did a complete zero-out of the drive with dd, and then I ran "badblocks -w" on the drive, which returned 0 bad blocks (not sure if this is really a good test for SSD's as there's some amount of internal voo-doo on the drive itself).
For future reference, how would I go about getting an image of the drive without being able to use btrfs-image?
Justin
____________________________________________________________
Car Insurance 18.29/Month
Get car insurance for as low as $18.29 a month.
http://thirdpartyoffers.netzero.net/TGL3231/4bbe24ec3a7bb18d3e5st01vuc
next reply other threads:[~2010-04-08 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 18:46 Justin [this message]
2010-04-09 11:18 ` btrfs Bug? Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2010-04-10 3:10 Justin
2010-04-12 14:03 ` Chris Mason
2010-04-07 0:37 yoosty69
2010-04-06 17:08 yoosty69
2010-04-08 14:04 ` Chris Mason
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=20100408.114640.18413.0@webmail01.vgs.untd.com \
--to=yoosty69@netzero.com \
--cc=chris.mason@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).