[btrfs-progs suspected BUG] Scrub info with Ubuntu-style subvol-as-root setup

2016-03-03 Thread boris
Hi, Setup: btrfs root but Ubuntu style: /@/ with root=@ as a kernel boot option. Been using it happily for years; not even sure if Ubuntu still uses this system for btrfs installs. btrfs fs is a partition on my GPT HDD. My fstab contains subvol=@ as option on the btrfs line,

Re: Changing label few times killed filesystem?

2014-11-27 Thread Boris Chernov
Since nobody had any other suggestions, I decided to attempt to run modified btrfsck with --repair option (without BUG_ON(rec-is_root) assertion). Surprisingly modified btrfsck --repair fixed all errors but one (according to btrfsck), but btrfsck asked me to run btrfsck --repair one

Re: Changing label few times killed filesystem?

2014-11-25 Thread Boris Chernov
On 2014-11-24 02:46, Duncan wrote if you were using gmane's web service, that explains things as weaverd, the process that does the threading on the web side, was down for some days Yes, I have used gmane blog. Good to know it is not down anymore. Back on topic. Even after updating

Re: Changing label few times killed filesystem?

2014-11-25 Thread Boris Chernov
In attempt to get more information, I have commented out BUG_ON(rec-is_root) in cmds-check.c to let btrfsck check my file system without failing on this assertion. Below you can see the output. I would appreciate any help or ideas... # btrfsck /dev/sdb1 # Full log can be downloaded

File test operator for subvols; possible bug in 'btrfs show directory'

2014-11-24 Thread boris
Hi all, I was looking for a quick method of testing whether a working directory is a subvolume. Couldn't see an obvious one, so tried 'btrfs show somesubvol≥'. It printed a fail message as expected but returned 0 exit status. Bug? Can I put in a feature request for a shell file test operator

Re: Changing label few times killed filesystem?

2014-11-23 Thread Boris Chernov
I suggest upgrading and just posting the results from 'btrfs check device' without any options and see what you get. OK, I have upgraded to 3.17.0 kernel and I also have upgraded btrfs-tools: # btrfs --version Btrfs v3.17 # btrfs check /dev/sdb1 Checking filesystem on /dev/sdb1 UUID:

Re: Changing label few times killed filesystem?

2014-11-21 Thread Boris Chernov
On 2014-11-21 04:35, Roman Mamedov wrote: On Fri, 21 Nov 2014 01:27:17 + Boris Chernov aqs1...@hotmail.com wrote: I have changed file system label few times in total. When I tried to mount it after that, it became not mountable: # mount /dev/sdb1 /mnt mount: Not a directory I'd say

Changing label few times killed filesystem?

2014-11-20 Thread Boris Chernov
I have changed file system label few times in total. When I tried to mount it after that, it became not mountable: # mount /dev/sdb1 /mnt mount: Not a directory In dmesg I see the following after above command: [ 5198.413202] BTRFS info (device sdb1): disk space caching is enabled [

Re: Massive BTRFS performance degradation

2014-03-09 Thread boris
Swâmi Petaramesh swami at petaramesh.org writes: Actually deduplication WAS the reason why I recently made the move to BTRFS again, for deduplication in ZFS is working, but *SO* memory hungry and performance killer unless you have *lots* of RAM... If you think about what dedup is has to