Chris Murphy posted on Sat, 22 Jul 2017 14:35:25 -0600 as excerpted:
> If we go back even further in time, what I'm trying to avoid is the
> problem with DE's where the user connects a two device Btrfs, and then
> they want to eject it. The DE is already confused because behind the
> scenes it has
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 volume. Add both device
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. Ph
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 devic
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 one
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 subcommand in 'btrfs' tool itse
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 subcommand in 'btrfs' tool itself. We can enhance the
>> documentation to state the expected pur
On Mon, Jul 17, 2017 at 9:54 AM, David Sterba wrote:
> On Fri, Jul 07, 2017 at 11:40:04AM -0600, Chris Murphy wrote:
>> On Fri, Jul 7, 2017 at 10:59 AM, Andrei Borzenkov
>> wrote:
>> > 07.07.2017 19:42, Chris Murphy пишет:
>> >> I'm digging through piles of list emails and not really finding an
On Fri, Jul 07, 2017 at 11:40:04AM -0600, Chris Murphy wrote:
> On Fri, Jul 7, 2017 at 10:59 AM, Andrei Borzenkov wrote:
> > 07.07.2017 19:42, Chris Murphy пишет:
> >> I'm digging through piles of list emails and not really finding an
> >> answer to this. Maybe it's Friday and I'm just confused...
On 2017-07-07 13:40, Chris Murphy wrote:
On Fri, Jul 7, 2017 at 10:59 AM, Andrei Borzenkov wrote:
07.07.2017 19:42, Chris Murphy пишет:
I'm digging through piles of list emails and not really finding an
answer to this. Maybe it's Friday and I'm just confused...
[root@f26s ~]# btrfs device re
On Fri, Jul 7, 2017 at 10:59 AM, Andrei Borzenkov wrote:
> 07.07.2017 19:42, Chris Murphy пишет:
>> I'm digging through piles of list emails and not really finding an
>> answer to this. Maybe it's Friday and I'm just confused...
>>
>>
>> [root@f26s ~]# btrfs device ready /dev/sda1
>> [root@f26s ~]
07.07.2017 19:42, Chris Murphy пишет:
> I'm digging through piles of list emails and not really finding an
> answer to this. Maybe it's Friday and I'm just confused...
>
>
> [root@f26s ~]# btrfs device ready /dev/sda1
> [root@f26s ~]# echo $?
> 0
> [root@f26s ~]# btrfs device ready /dev/mapper/vg
I'm digging through piles of list emails and not really finding an
answer to this. Maybe it's Friday and I'm just confused...
[root@f26s ~]# btrfs device ready /dev/sda1
[root@f26s ~]# echo $?
0
[root@f26s ~]# btrfs device ready /dev/mapper/vg-1
[root@f26s ~]# echo $?
0
/dev/sda1 is a single de
13 matches
Mail list logo
