All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mason <chris.mason@oracle.com>
To: Denys Fedoryschenko <denys@visp.net.lb>
Cc: linux-ext4@vger.kernel.org, Josef Bacik <jbacik@redhat.com>
Subject: Re: btrfs BUG() & panic in __btrfs_reserve_extent(), 2.6.30-rc6
Date: Tue, 26 May 2009 06:05:40 -0400	[thread overview]
Message-ID: <20090526100540.GB25835@think> (raw)
In-Reply-To: <200905241347.31054.denys@visp.net.lb>

On Sun, May 24, 2009 at 01:47:30PM +0300, Denys Fedoryschenko wrote:
> Hardware: 2x Core 2 Quad Xeon, RAM 8GB, 9 HDD
> Arch: x86_64
> Distro: custom, almost embedded
> Kernel: 2.6.30-rc6-git6-build-0045-64bit
> 
> netconsole crash information: http://www.nuclearcat.com/files/btrfs-crash.txt

Josef, it looks like the tracking code is losing some bytes ;)  The
total bytes in the space info doesn't add up to the other numbers in
this data.  It is worth mentioning that he's doing nodatacow.

Definitely a btrfs bug, so we can trim ext4 off the list from now on,
full quote below for Josef.

-chris

> 
> df information:
> Proxy-Karam-Main /config # df -h
> Filesystem                Size      Used Available Use% Mounted on
> /dev/mapper/root          3.6G    107.1M      3.4G   3% /mnt/flash
> /dev/loop0                4.9M      4.9M         0 
> 100% /lib/modules/2.6.30-rc6-git6-build-0045-64bit
> /dev/sdb2               118.9G     17.6G     95.2G  16% /cache2
> /dev/sdc1               134.5G     17.6G    110.0G  14% /cache3
> /dev/sdd1               134.5G     17.6G    110.0G  14% /cache4
> /dev/sde1               134.5G     17.6G    110.0G  14% /cache5
> /dev/sdf1               134.5G     17.8G    109.9G  14% /cache6
> /dev/sdg1               134.5G     17.6G    110.0G  14% /cache7
> /dev/sdh1               134.5G     17.4G    110.2G  14% /cache8
> /dev/sdb1                15.8G      9.4G      6.5G  59% /cache9
> /dev/sda1                15.8G      9.4G      6.5G  59% /cache10
> 
> Proxy-Karam-Main /config # df -i
> Filesystem              Inodes      Used Available Use% Mounted on
> /dev/mapper/root        243360        36    243324   0% /mnt/flash
> /dev/loop0                 840       840         0 
> 100% /lib/modules/2.6.30-rc6-git6-build-0045-64bit
> /dev/sdb2              7921664     38420   7883244   0% /cache2
> /dev/sdc1              8953856     39806   8914050   0% /cache3
> /dev/sdd1              8953856     38571   8915285   0% /cache4
> /dev/sde1              8953856     38829   8915027   0% /cache5
> /dev/sdf1              8953856     50827   8903029   1% /cache6
> /dev/sdg1              8953856     41111   8912745   0% /cache7
> /dev/sdh1              8953856     28609   8925247   0% /cache8
> /dev/sdb1                    0         0         0   0% /cache9
> /dev/sda1                    0         0         0   0% /cache10
> 
> /proc/mounts
> Proxy-Karam-Main /config # cat /proc/mounts
> rootfs / rootfs rw 0 0
> proc /proc proc rw,relatime 0 0
> sysfs /sys sysfs rw,relatime 0 0
> none /dev/pts devpts rw,relatime,mode=600 0 0
> none /proc/bus/usb usbfs rw,relatime 0 0
> /dev/mapper/root /mnt/flash ext3 rw,noatime,errors=continue,data=writeback 0 0
> /dev/loop0 /lib/modules/2.6.30-rc6-git6-build-0045-64bit squashfs ro,relatime 
> 0 0
> /dev/sdb2 /cache2 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sdc1 /cache3 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sdd1 /cache4 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sde1 /cache5 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sdf1 /cache6 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sdg1 /cache7 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sdh1 /cache8 ext4 
> rw,noatime,nodiratime,commit=60,barrier=1,journal_async_commit,data=writeback 
> 0 0
> /dev/sdb1 /cache9 btrfs rw,relatime,nodatasum,nodatacow,nobarrier,noacl 0 0
> /dev/sda1 /cache10 btrfs rw,relatime,nodatasum,nodatacow,nobarrier,noacl 0 0
> 
> btrfs-show
> Label: CACHE10  uuid: de61670d-5e6a-40f1-8712-aaa4bf3df719
>         Total devices 1 FS bytes used 9.36GB
>         devid    1 size 15.83GB used 15.83GB path /dev/sda1
> 
> Label: CACHE9  uuid: a293c4d3-31d6-427e-9cbf-5e5fbaf8871e
>         Total devices 1 FS bytes used 9.37GB
>         devid    1 size 15.83GB used 15.83GB path /dev/sdb1
> 
> 

  reply	other threads:[~2009-05-26 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 10:47 btrfs BUG() & panic in __btrfs_reserve_extent(), 2.6.30-rc6 Denys Fedoryschenko
2009-05-26 10:05 ` Mason [this message]
2009-05-26 10:05   ` Denys Fedoryschenko

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=20090526100540.GB25835@think \
    --to=chris.mason@oracle.com \
    --cc=denys@visp.net.lb \
    --cc=jbacik@redhat.com \
    --cc=linux-ext4@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.