[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] Running docker-storage-setup from a UI
- From: Marius Vollmer <marius vollmer redhat com>
- To: "Vivek Goyal" <vgoyal redhat com>
- Cc: atomic-devel projectatomic io
- Subject: Re: [atomic-devel] Running docker-storage-setup from a UI
- Date: Mon, 18 Apr 2016 12:02:49 +0300
Vivek Goyal <vgoyal redhat com> writes:
> On Fri, Apr 15, 2016 at 02:46:24PM +0300, Marius Vollmer wrote:
>
>> Sorry, I was talking about d-s-s. Do you think it is a bug in d-s-s
>> that pvcreate might prompt during its run and make it fail in a
>> non-interactive use?
>
> No it is not a bug. If user provided a disk to dss which alrady has
> signatures from other tools, we will not use that disk for thin
> pool. One needs to wipe all the signatures and then provide that disk
> to dss.
Just to repeat this (and then I shut up :-), in my case pvcreate found a
obsolete and unaccessible signature somewhere in the middle of a disk
that didn't have a partition table and looked empty to everyone involved
when it was given to d-s-s. The disk did not contain a xfs partition,
just a random, left-over signature that happened to be at the right
place for the partition that d-s-s has created.
> dss being a service does not mean it will automatically wipe off any
> exisitng signatures on disk. It is very risky. I am not sure why are
> you taking it so lightly.
Because the current behavior of d-s-s in this area feels more like an
accident than design, and I had assumed it was unintended.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]