From: Jan Killius <tmpnerd@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: corruption with btrfs on nocow loop file
Date: Thu, 18 Sep 2014 16:06:49 +0200 [thread overview]
Message-ID: <CACe732sS7bTvVCQm3f2BQagsqad+RFwRXhhiaGh+f2tDPupuVA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Hello,
I get corruption with btrfs in a loop device with linux-3.16.3
(https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/
for-linus applied).
I never had a problem with this setup until 3.16.
This happened just after unpacking a few thousand small files and
reading them back with an IDE (phpstorm).
The loop file is a 50GB nocow file with LUKS on it.
mount options for the main btrfs filesystem:
/dev/sda2 on / type btrfs
(rw,noatime,compress-force=lzo,ssd,discard,noacl,space_cache)
mount options for the loop device:
/dev/mapper/myvolume on /mnt/volume type btrfs
(rw,noatime,compress-force=lzo,ssd,noacl,space_cache)
btrfsck:
Checking filesystem on /dev/mapper/npoa
UUID: 3a869f74-2a05-4ea2-9950-a6be5e4a9691
checking extents
checking free space cache
checking fs roots
checking csums
checking root refs
found 197030750 bytes used err is 0
total csum bytes: 1245628
total tree bytes: 133332992
total fs tree bytes: 127696896
total extent tree bytes: 3997696
btree space waste bytes: 22086930
file data blocks allocated: 1277382656
referenced 2252468224
Btrfs v0.20-rc1-592-ge11a9ae-dirty
I also got a btrfs-image of the loop file system if needed.
If more information's are needed to investigate the issue just ask.
Kindly regards
Jan Killius
[-- Attachment #2: dmesg.bz2 --]
[-- Type: application/x-bzip2, Size: 19008 bytes --]
reply other threads:[~2014-09-18 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACe732sS7bTvVCQm3f2BQagsqad+RFwRXhhiaGh+f2tDPupuVA@mail.gmail.com \
--to=tmpnerd@gmail.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).