I just had another big freeze ... I could change to a terminal and sysrq-triggering gave this: http://pastebin.com/F1jQqtUQ
2013/2/8 Florian Hofmann <fhofm...@techfak.uni-bielefeld.de>: > Oh ... I should have mentioned that btrfs is running on top of LUKS. > > 2013/2/8 Florian Hofmann <fhofm...@techfak.uni-bielefeld.de>: >> $ btrfs fi df / >> Data: total=165.00GB, used=164.19GB >> System, DUP: total=32.00MB, used=28.00KB >> System: total=4.00MB, used=0.00 >> Metadata, DUP: total=2.00GB, used=1.40GB >> >> $ btrfs fi show >> failed to read /dev/sr0 >> Label: none uuid: b4ec0b14-2a42-47e3-a0cd-1257e789ed25 >> Total devices 1 FS bytes used 165.59GB >> devid 1 size 600.35GB used 169.07GB path /dev/dm-0 >> >> Btrfs Btrfs v0.19 >> >> --- >> >> I just noticed that I can force 'it' by transferring a large file from >> my NAS. I did the sysrq-trigger thing, but there is no suspicious >> output in dmesg (http://pastebin.com/swrCdC3U). >> >> Anything else? >> >> 2013/2/8 Josef Bacik <jba...@fusionio.com>: >>> On Fri, Feb 08, 2013 at 02:30:04PM -0700, Florian Hofmann wrote: >>>> Hi everybody, >>>> >>>> I am using btrfs as my main fs for some time now, but I am >>>> experiencing severe performance drawbacks. I can't qualify the >>>> circumstances, but sometimes during disc access the whole system >>>> freezes for some time. >>>> >>>> Maybe somebody could suggest some general things I could try to search >>>> for the problem? >>> >>> Can I see >>> >>> btrfs fi df /mnt/point >>> btrfs fi show >>> >>> and then when you are having problems >>> >>> echo w > /proc/sysrq-trigger >>> >>> and capture dmesg. Thanks, >>> >>> Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
