From: Maciej Marcin Piechotka <uzytkownik2@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/inode.c:2299
Date: Sat, 17 Sep 2011 20:25:02 +0200 [thread overview]
Message-ID: <1316283907.3253.8.camel@picard> (raw)
In-Reply-To: <1314582311.2724.4.camel@picard>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
1. Once the blank screen happened ot 23:00 UTC instead of 03:00 UTC
2. I tried to disable the caches
3. I tried to rsync via ext3 + btrfs-convert. I noticed something - in
old fs the df looked like:
Data: total=30.01GB, used=28.42GB
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=199.47MB
Metadata: total=8.00MB, used=0.00
on new one (with ext3 image):
Data: total=33.33GB, used=20.52GB
System: total=32.00MB, used=4.00KB
Metadata: total=16.64GB, used=11.36GB
and without:
Data: total=33.33GB, used=20.04GB
System: total=32.00MB, used=4.00KB
Metadata: total=16.64GB, used=10.88GB
Given that lzo compression was used about 4 GB data difference was
expected (difference depending on mount options on rsynbc). However:
1. What is DUP?
2. Why metadata is so big on convertion from ext3 while data is small
(the sum is about right - 31GB vs 28.5GB)?
Regards
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-09-17 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 1:45 kernel BUG at fs/btrfs/inode.c:2299 Maciej Marcin Piechotka
2011-08-30 6:27 ` Miao Xie
2011-08-30 8:47 ` Maciej Marcin Piechotka
2011-09-02 11:18 ` Maciej Marcin Piechotka
2011-09-05 13:47 ` Maciej Marcin Piechotka
2011-09-09 1:13 ` Maciej Marcin Piechotka
2011-09-09 3:02 ` Roman Mamedov
2011-09-09 3:29 ` Maciej Marcin Piechotka
2011-09-19 0:44 ` Maciej Marcin Piechotka
2011-09-21 2:14 ` Maciej Marcin Piechotka
2011-09-17 18:25 ` Maciej Marcin Piechotka [this message]
2011-09-17 18:30 ` Maciej Marcin Piechotka
2011-09-18 0:08 ` Maciej Marcin Piechotka
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=1316283907.3253.8.camel@picard \
--to=uzytkownik2@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).