From: "sepero111@gmx.com" <sepero111@gmx.com>
To: linux-btrfs@vger.kernel.org
Subject: Especially broken btrfs
Date: Thu, 20 Mar 2014 23:21:27 -0400 [thread overview]
Message-ID: <532BB037.90401@gmx.com> (raw)
Hello all. I submit bugs to different foss projects regularly, but I don't
really have a bug report this time. I have a broken filesystem to report. And I
have no idea how to reproduce it.
I am including a link to the filesystem itself, because it appears to be
unrepairable and unrestorable. I have no personal information on the disk image.
The filesystem is almost 512MB uncompressed. I was using it on an old usb drive
with 512MB size limitation. I only used (abused?) it about 2 days before this
corruption.
My goal was to use the usb as a bootable rescue system. I decided to try Btrfs
instead of Ext4, because it supports filesystem compression.
BTRFS IMAGE LINK (please pardon my file hosting service)
http://www.mediafire.com/download/gdaydt3mz8uwtmm/sdb1.btrfs.xz
These are some things that may have helped to cause the corruption.
+Created btrfs with -M flag
+Installed Debian testing/unstable
+When mounting, I always used at least these options:
ssd_spread,noatime,compression=zlib,autodefrag
+Occasionally force powering off computer.
+While booted into usb system, I was constantly running out of space while
trying to install new packages.
It is my hope that this image might be used to improve the btrfs restore and
btrfsck tools. Please let me know if I can provide any further information. Big
thanks to everyone helping to further development of Btrfs.
Sepero
next reply other threads:[~2014-03-21 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 3:21 sepero111 [this message]
2014-03-30 4:50 ` Especially broken btrfs Marc MERLIN
2014-03-31 16:21 ` sepero111
2014-03-31 17:04 ` Bob Marley
2014-03-31 18:28 ` Duncan
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=532BB037.90401@gmx.com \
--to=sepero111@gmx.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 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.