Am Dienstag, 20. Dezember 2011 schrieb Martin Steigerwald: > Hi again! […] > Am Samstag, 17. Dezember 2011 schrieb Martin Steigerwald: > > Hi! > > > > Finally I tried scrubbing the / BTRFS filesystem mentioned in the > > thread "speeding up slow btrfs filesystem". However the machine looks > > up hard then. It repeats the last few seconds of audio all over > > again, no mouse and no ssh connection anymore: > > > > deepdance:~> btrfs scrub start / > > scrub started on /, fsid […] (pid=5737) > > deepdance:~> Write failed: Broken pipe > > > > > > After the second attempt of doing this the machine stops on booting > > after the space cache enabled message. Then I get backtraced of hung > > tasks: > > > > http://martin-steigerwald.de/tmp/btrfs/2011-17-12-deepdance-hang-at-b > > oot/ > > > > > > I am able to mount the filesystem from grml 2011.12-rc1 with 3.1 > > kernel:
I still have this with 3.2.0-1-pae - which is a debian kernel based on 3.2.1. When I do btrfs scrub start / the machine locks immediately up hard. Then usually on next boot it stops on space_cache enabled message, but not the one for /, but the one for /home which is mounted later. When I then boot with 3.1 it works. BTRFS redos the space_cache then while the machine takes ages to boot - I mean ages - 10 minutes till KDM prompt is no problem there. I thought I just mention it here. Since I got no hints on what to do, I probably redo both filesystems on the machine. Should that not work out, I switch the box to Ext4. btrfs filesystem scrub works on my ThinkPad T520 with 64-bit debian and Intel SSD 320 and one 2,5 inch external drive as well as a 3,5 inch external backup drive both via eSATA, so this seems to be no principal issue. It also works on a workstation at work which has 32-bit debian as well. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- 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
