Re: degraded raid scribbling upon wrong device

2017-07-22 Thread Adam Borowski
On Thu, Jul 13, 2017 at 08:40:12AM +0200, Adam Borowski wrote: > Here's a set of test cases, two of them in some cases seem to scribble upon > the wrong device: > > * deg-mid-missing > * deg-last-replaced (not on the innocent "re") > * but never deg-last-missing > > When all goes ok, there are

Re: btrfs device ready purpose

2017-07-22 Thread Chris Murphy
On Sat, Jul 22, 2017 at 1:58 PM, Adam Borowski wrote: > On Sat, Jul 22, 2017 at 06:15:58PM +, Hugo Mills wrote: >> On Sat, Jul 22, 2017 at 12:06:17PM -0600, Chris Murphy wrote: >> > I just did an additional test that's pretty icky behavior. >> > >> > 2x HDD device Btrfs

Re: btrfs device ready purpose

2017-07-22 Thread Adam Borowski
On Sat, Jul 22, 2017 at 06:15:58PM +, Hugo Mills wrote: > On Sat, Jul 22, 2017 at 12:06:17PM -0600, Chris Murphy wrote: > > I just did an additional test that's pretty icky behavior. > > > > 2x HDD device Btrfs volume. Add both devices and `btrfs devices ready` > > exits with 0 as expected.

Re: btrfs device ready purpose

2017-07-22 Thread Hugo Mills
On Sat, Jul 22, 2017 at 12:06:17PM -0600, Chris Murphy wrote: > I just did an additional test that's pretty icky behavior. > > 2x HDD device Btrfs volume. Add both devices and `btrfs devices ready` > exits with 0 as expected. Physically remove both USB devices. > Reconnect one device. `btrfs

Re: btrfs device ready purpose

2017-07-22 Thread Chris Murphy
I just did an additional test that's pretty icky behavior. 2x HDD device Btrfs volume. Add both devices and `btrfs devices ready` exits with 0 as expected. Physically remove both USB devices. Reconnect one device. `btrfs device ready` still exits 0. That's definitely not good. (If I leave that

Re: btrfs device ready purpose

2017-07-22 Thread Chris Murphy
On Fri, Jul 21, 2017 at 11:55 PM, Andrei Borzenkov wrote: > 21.07.2017 17:36, Chris Murphy пишет: >>> >>> The command is just a simple wrapper around the DEVICES_READY ioctl, but >>> now that systemd has it's own wrapper tool, there are probably no users >>> of that

Re: [PATCH v3 0/4] Add xxhash and zstd modules

2017-07-22 Thread Adam Borowski
On Fri, Jul 21, 2017 at 11:56:21AM -0400, Austin S. Hemmelgarn wrote: > On 2017-07-20 17:27, Nick Terrell wrote: > > This patch set adds xxhash, zstd compression, and zstd decompression > > modules. It also adds zstd support to BtrFS and SquashFS. > > > > Each patch has relevant summaries,

Re: How to detect "orphaned" subvolume attachment point in snapshot?

2017-07-22 Thread Hans van Kranenburg
On 07/22/2017 09:58 AM, Andrei Borzenkov wrote: > Here is structure of snapshots in openSUSE; all snapshots of root volume > are created under /.snapshots subvolume: > > linux-gtrk:/host/home/src/python-btrfs/examples # sudo mount -o > ro,subvol=/ /dev/sda3 /mnt >

How to detect "orphaned" subvolume attachment point in snapshot?

2017-07-22 Thread Andrei Borzenkov
Here is structure of snapshots in openSUSE; all snapshots of root volume are created under /.snapshots subvolume: linux-gtrk:/host/home/src/python-btrfs/examples # sudo mount -o ro,subvol=/ /dev/sda3 /mnt linux-gtrk:/host/home/src/python-btrfs/examples # ./show_directory_contents.py /mnt/

Re: kernel btrfs file system wedged -- is it toast?

2017-07-22 Thread Marat Khalili
> The btrfs developers should have known this, and announced this, a long time ago, in various prominent ways that it would be difficult for potential new users to miss.  I'm also a user like you, and I felt like this too when I came here (BTW there are several traps in BTRFS, and other are