All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: hard freezes with 3.9.0 during io-intensive loads
Date: Sun, 5 May 2013 20:39:53 -0400	[thread overview]
Message-ID: <20130506003953.GH12414@localhost.localdomain> (raw)
In-Reply-To: <6moh5a-knf.ln1@hurikhan.ath.cx>

On Sun, May 05, 2013 at 04:25:45AM -0600, Kai Krakow wrote:
> Hello list,
> 
> I've upgraded to 3.9.0 mainly for the snapshot-aware defragging patches. I'm 
> running bedup[1] on a regular basis and it is now the third time that I got 
> back to my PC just to find it hard-frozen and I needed to use the reset 
> button.
> 
> It looks like this happens only while running bedup on my two btrfs 
> filesystems but I'm not sure if it happens for any of the filesystems or 
> only one. This is my setup:
> 
> # cat /etc/fstab (shortened)
> UUID=d2bb232a-2e8f-4951-8bcc-97e237f1b536 / btrfs compress=lzo,subvol=root64 
> 0 1 # /dev/sd{a,b,c}3
> LABEL=usb-backup /mnt/private/usb-backup btrfs noauto,compress-
> force=zlib,subvolid=0,autodefrag,comment=systemd.automount 0 0 # external 
> usb3 disk
> 
> # btrfs filesystem show
> Label: 'usb-backup'  uuid: 7038c8fa-4293-49e9-b493-a9c46e5663ca
>         Total devices 1 FS bytes used 1.13TB
>         devid    1 size 1.82TB used 1.75TB path /dev/sdd1
> 
> Label: 'system'  uuid: d2bb232a-2e8f-4951-8bcc-97e237f1b536
>         Total devices 3 FS bytes used 914.43GB
>         devid    3 size 927.26GB used 426.03GB path /dev/sdc3
>         devid    2 size 927.26GB used 426.03GB path /dev/sdb3
>         devid    1 size 927.26GB used 427.07GB path /dev/sda3
> 
> Btrfs v0.20-rc1
> 
> Since the system hard-freezes I have no messages from dmesg. But I suspect 
> it to be related to the defragmentation option in bedup (I've switched to 
> bedub with --defrag since 3.9.0, and autodefrag for the backup drive). Just 
> in case, I'm going to try without this option now and see if it won't 
> freeze.
> 
> I was able to take a "physical" screenshot with a real camera of a kernel 
> backtrace one time when the freeze happened. I wonder if it is useful to you 
> and where to send it. I just don't want to upload jpegs right here to the 
> list without asking first.
> 
> The big plus is: Altough I had to hard-reset the frozen system several times 
> now, btrfs survived the procedure without any impact (just boot times 
> increases noticeably, probably due to log-replays or something). So thumbs 
> up for the developers on that point.
> 
> [1]: https://github.com/g2p/bedup
> 

Can you please file a bug for this issue on bugzilla.kernel.org so I can make
sure we don't lose track of it?  Make sure the component is set to Btrfs.
Thanks,

Josef

  parent reply	other threads:[~2013-05-06  0:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 10:25 hard freezes with 3.9.0 during io-intensive loads Kai Krakow
2013-05-05 16:10 ` Kai Krakow
2013-05-05 18:33   ` cwillu
2013-05-06  8:55   ` Jan Schmidt
2013-05-06  9:12     ` Harald Glatt
2013-05-06 20:29     ` Kai Krakow
2013-05-07  6:08       ` Jan Schmidt
2013-05-07 21:16         ` Kai Krakow
2013-05-08  0:24           ` Kai Krakow
2013-05-08 11:05             ` Jan Schmidt
2013-05-09 23:30               ` Kai Krakow
2013-05-10  7:01                 ` Jan Schmidt
2013-05-11 10:01                   ` Kai Krakow
2013-05-16  7:19                   ` Kai Krakow
2013-05-17 15:43                     ` Jan Schmidt
2013-05-06  0:39 ` Josef Bacik [this message]
2013-05-06  7:47   ` Kai Krakow

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=20130506003953.GH12414@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=hurikhan77+btrfs@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 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.