Hello group, both problems I struggled with were discussed in the past. Due to recent discussion and different problems with btrfs builtin experimental raid, I decided to go to btrfs on md-raid (again, as I noticed later). I created a RAID 1 array, and created a new btrfs filesystem and created opensuse-style subvolumes. Restored my backup. Everything seemed to work fine... But after reboot, the btrfs filesystem is faulty and can't be repaired with btrfs check (does not complete, will segfault). It seems, that much data wasn't written to the hdds (missing transactions...). In a discussion two years ago, the assumption was a "write hole". In fact the SATA controller is being reset occassionally.. never had problems with that fact using ext3/ext4/reiserfs. Two years ago I switched to btrfs raid. But it was very problematically (missing implementations, no hot spare, ...) and also ended somewhen in fatal error.. Now, I am wondering if there is a good alternative filesystem? I like the subvolume management, which is easier to maintain as lvm, in my opinion. Important also snapshots and especially the cow-feature. Does anyone have tips? how can this write-hole problem be solved? any possibility to monitor/check filesystem while mounted? to get a working system again, any commands available to clear the filesystem contents, but leave the structure (subvolumes) intact? Thank you Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org