Jan Schmidt <list.bt...@jan-o-sch.net> schrieb: >> Apparently, it's not fixed. The system does not freeze now but it threw >> multiple backtraces right in front of my Xorg session. The backtraces >> look a little bit different now. Here's what I got: >> >> https://gist.github.com/kakra/8a340f006d01e146865d >> >> Occurence while running "bedup dedup --defrag --size-cutoff >> $((1024*1024))" which was currently dedup'ing my backup volume with daily >> snapshots filled by "rsync --inplace" - so I suppose some file contents >> are pretty scattered. > > At least that looks different for now. I'm not certain about all the fixes > in btrfs-next. Can you give it a try and bisect if btrfs-next is good? > That would be really helpful.
I'd prefer to not bisect my production system kernel... That will probably take ages as running the "reproducable test" takes about 30-60 minutes before the problem hits my system. At least unless you had a suggestion how to speed up the process... ;-) I saw the pull request with those fixes, so I supsect it didn't go into 3.9.1 but rather will go into 3.9.2? I probably wait and just do not run the dedup process until I have 3.9.2 installed. The backup works with occassional hiccups, the system very very sometimes freezes but I almost always see the backtraces in dmesg after backup. Let's see if it's all gone in 3.9.2. Regards, Kai -- 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
