On Fri, Feb 8, 2013 at 4:56 PM, Florian Hofmann <fhofm...@techfak.uni-bielefeld.de> wrote: > 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?
The pastebin didn't include any output from sysrq-w; even if there's nothing to report there would still be a dozen lines or so per cpu; at the absolute minimum there should be a line for each time you ran it: [4477369.680307] SysRq : Show Blocked State Note that you need to echo as root, or use the keyboard combo alt-sysrq-w to trigger. -- 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
