On Thu, May 18, 2017 at 9:18 AM, Eric A. Borisch wrote:
> On Wed, May 17, 2017 at 9:38 PM, Eric A. Borisch
> wrote:
>
>> 4) zpool import -f alpha beta succeeds without any complaints.
>>
>> IV. Alpha no longer exists, Beta exists (with the same GUID as
On Wed, May 17, 2017 at 9:38 PM, Eric A. Borisch wrote:
> 4) zpool import -f alpha beta succeeds without any complaints.
>
> IV. Alpha no longer exists, Beta exists (with the same GUID as Alpha) AND
> is active. This is an 'atomic' operation from user's point of view, and at
> On May 17, 2017, at 2:13 PM, Brandon Allbery wrote:
>
> Sorry, no, that's not a bug. The bug is that, if importing on another
> system is a common administrative operation, it should not require you to
> disable *all* checking. I'd rather prefer specific support for that,
On Wed, May 17, 2017 at 8:27 PM Paul Kraus wrote:
>
> > On May 17, 2017, at 5:12 PM, Eric A. Borisch wrote:
> >
> > Short version:
> >
> > It's not the -f causing the problem, it's the parsing and (double)
> > importing via /boot/zfs/zpool.cache that is.
> On May 17, 2017, at 5:12 PM, Eric A. Borisch wrote:
>
> Short version:
>
> It's not the -f causing the problem, it's the parsing and (double)
> importing via /boot/zfs/zpool.cache that is.
I was unclear… _how_ do you get the double entry in zpool.cache _except_ by
using
On Tue, May 16, 2017 at 8:53 PM, Paul Kraus wrote:
>
>
> > On May 16, 2017, at 10:26 AM, Eric A. Borisch
wrote:
> >
> > On Tue, May 16, 2017 at 1:31 AM, Trond Endrestøl <
> > trond.endres...@fagskolen.gjovik.no> wrote:
> >
> >> I guess you had a
On 05/16/2017 04:26 PM, Eric A. Borisch wrote:
On Tue, May 16, 2017 at 1:31 AM, Trond Endrestøl <
trond.endres...@fagskolen.gjovik.no> wrote:
I guess you had a /boot/zfs/zpool.cache file referring to the original
zroot pool. Next, the kernel found the vega pool and didn't realise
these two
On Wed, May 17, 2017 at 2:04 PM, Nikos Vassiliadis wrote:
> If you boot from another system, there is no other way to
> import a pool than using "import -f". So, I guess it is
> part of normal administrative tasks. You can read more here:
>
>
On 05/16/2017 05:08 PM, Fabian Keil wrote:
Why did you use the -f flag? Unless you can reproduce the
problem without it, it's not obvious to me that this is a
bug.
If you boot from another system, there is no other way to
import a pool than using "import -f". So, I guess it is
part of normal
> On May 16, 2017, at 10:26 AM, Eric A. Borisch wrote:
>
> On Tue, May 16, 2017 at 1:31 AM, Trond Endrestøl <
> trond.endres...@fagskolen.gjovik.no> wrote:
>
>> I guess you had a /boot/zfs/zpool.cache file referring to the original
>> zroot pool. Next, the kernel found the
Nikos Vassiliadis wrote:
> On 05/15/2017 08:09 PM, Nikos Vassiliadis wrote:
> > Hi everybody,
> >
> > While trying to rename a zpool from zroot to vega,
> > I ended up in this strange situation:
> > nik@vega:~ % zfs list -t all
> > NAME USED AVAIL REFER
On Tue, May 16, 2017 at 1:31 AM, Trond Endrestøl <
trond.endres...@fagskolen.gjovik.no> wrote:
> I guess you had a /boot/zfs/zpool.cache file referring to the original
> zroot pool. Next, the kernel found the vega pool and didn't realise
> these two pools are the very same.
>
Assuming this is
On Mon, 15 May 2017 20:11+0200, Nikos Vassiliadis wrote:
> Fix the e-mail subject
>
> On 05/15/2017 08:09 PM, Nikos Vassiliadis wrote:
> > Hi everybody,
> >
> > While trying to rename a zpool from zroot to vega,
> > I ended up in this strange situation:
> > nik@vega:~ % zfs list -t all
> > NAME
Fix the e-mail subject
On 05/15/2017 08:09 PM, Nikos Vassiliadis wrote:
Hi everybody,
While trying to rename a zpool from zroot to vega,
I ended up in this strange situation:
nik@vega:~ % zfs list -t all
NAME USED AVAIL REFER MOUNTPOINT
vega1.83G 34.7G
14 matches
Mail list logo