zfs-dev wrote:
You might want to try a reboot of the system. There is some low level
caching of the encryption key in the kernel. I noticed that you can
remove the key and continue to mount and umount it without a key so long
as you do not reboot. Maybe this will clear it up. I never recommend
Darren J Moffat wrote:
...
Can you send the 'zpool history slice_2' output so I can see what
commands have been run.
Pasted at the end - My recollection of the events was
wrong, I started with "keysource=passphrase,file..."
not prompt. (Used prompt in earlier experiments and
mixed things up)
On Tue, Feb 21, 2012 at 11:12:14AM +, Darren J Moffat wrote:
> Did you ever do a send|recv of these filesystems ? There was a bug with
> send|recv in 151a that has since been fixed that could cause the salt to
> be zero'd out in some cases.
Ah, so that's what that was.
I hit this problem
On 02/18/2012 04:00 AM, zfs-discuss-requ...@opensolaris.org wrote:
Message: 2
Date: Sat, 18 Feb 2012 00:12:44 -0500
From: Roberto Waltman
To:zfs-discuss@opensolaris.org
Subject: [zfs-discuss] Cannot mount encrypted filesystems.
Message-ID:<4f3f334c.4090...@rwaltman.com>
Content-Type: text/plain;
On 02/21/12 13:27, Edward Ned Harvey wrote:
From: Darren J Moffat [mailto:darr...@opensolaris.org]
Sent: Monday, February 20, 2012 12:46 PM
GRUB2 has support
for encrypted ZFS file systems already.
I assume this requires a pre-boot password, right? Then I have two
questions...
The ZFS enc
> From: Darren J Moffat [mailto:darr...@opensolaris.org]
> Sent: Monday, February 20, 2012 12:46 PM
>
> GRUB2 has support
> for encrypted ZFS file systems already.
I assume this requires a pre-boot password, right? Then I have two
questions...
I noticed in solaris 11, when you "init 6" it doesn
In message <4f435ca9.8010...@tuneunix.com>, nathank writes:
>Is there actually a fix to allow manual setting of ashift now that I
No.
http://docs.oracle.com/cd/E23824_01/html/821-1462/zpool-1m.html>
John
groenv...@acm.org
___
zfs-discuss mailing list
z
On 02/21/12 01:58, Roberto Waltman wrote:
First, I did the 2nd. (Change location only)
I believe I tried the first form also *after*
things were already broken, but I'm sure the
passphrases were identical: slice_08, slice_18
and slice_28 for each pools 0/1/2. - The '8'
to bring the length to the
Hang on -
IIRC, it's only yes to that question if the drive itself advertises that
it's 4K sectors.
I believed that if it uses 4K sectors, but *advertises* that it uses 512
byte blocks, then it goes to crap pretty quickly. (witness Netapp FC
luns, many SSD's etc)
Is there actually a fix to
