question about btrfsck/mount behavior on corrupted fs

question about btrfsck/mount behavior on corrupted fs

[Ondrej Kozina]

Hi all,

I've been playing with btrfs resize recently and run into strange 
looking behavior to me. One of my simple test scenario was following:

- partition some block device (lets say sda sectors 2-2000 are sda1)
- try to create btrfs on top of it (just mkfs.btrfs /dev/sda1)
- fill the fs with data
- unmount the device
- let's simulate usual mistake here: downsize the partition with btrfs 
filesystem w/o proper btrfs resize command. In fact I moved the 
beginning of the sda2 partition into middle of former sda1. so now it 
looks like: 2-1000 sda1, 1001-2000 sda2.
- remount the fs

I was surprised both commands btrfsck and mount were successful w/o any 
error report even in syslog. Does it work as intended? Do you plan to 
support some sort of checks during mount/btrfsck? Possibly a new feature 
in btrfsck utility to warn the user something ugly happened to his fs? 
Is there any way to fix broken fs like this (supposing the cut off area 
didn't contain allocated blocks)?

Kind regards
Ondrej