Mark J Musante wrote:
> Alan, can you point me at your machine (if it's on SWAN)? I'd like to
> see what's going on in there.
Many thanks to Mark for his help, I eventually figured out the problem:
6730154 Grub: findroot fails to find ZFS BE
Precis: USB disks, LU & ZFS boot don't mix.
--
Al
Mark J Musante wrote:
> Alan, can you point me at your machine (if it's on SWAN)? I'd like to
> see what's going on in there.
Might be easiest to use sun shared shell to get you access...
--
Alan Burlison
--
___
zfs-discuss mailing list
zfs-discuss@
On Fri, 25 Jul 2008, Alan Burlison wrote:
> Enda O'Connor wrote:
>
>> probably
>> 6722767 lucreate did not add new BE to menu.lst ( or grub )
>
> Yeah, I found that bug, added A CR & bumped the priority.
> Unfortunatrly there's no analysis or workaround in the bug, so I've no
> idea what the rea
Mark J Musante wrote:
> As a workaround, you can pre-create the swap & dump zvols. E.g.:
>
> zfs create -V 512m {pool}/swap
> zfs create -V 2g {pool}/dump
>
> If LU sees that the zvols already exist, it assumes they are correctly
> sized.
Nice tip, thanks :-)
--
Alan Burlison
--
___
Enda O'Connor wrote:
> probably
> 6722767 lucreate did not add new BE to menu.lst ( or grub )
Yeah, I found that bug, added A CR & bumped the priority. Unfortunatrly
there's no analysis or workaround in the bug, so I've no idea what the
real problem is.
--
Alan Burlison
--
__
On Thu, 24 Jul 2008, Alan Burlison wrote:
>> What if you turned slice 1 into a pool (a new one), migrated your BE
>> into it, then grow that pool to soak up the space in the slices that
>> follow it? You might still need to save some stuff elsewhere while
>> you're doing the transition.
>
> Doe
Alan Burlison wrote:
> Lori Alt wrote:
>
>> It's hard to know what the "right" thing to do is from within
>> the installation software. Does the user want to preserve
>> as much of their current environment as possible? Or does
>> the user want to move toward the new "standard" configuration
>>
Lori Alt wrote:
> It's hard to know what the "right" thing to do is from within
> the installation software. Does the user want to preserve
> as much of their current environment as possible? Or does
> the user want to move toward the new "standard" configuration
> (which is pretty much zfs-ever
Lori Alt wrote:
> Sounds like LU needs some of the same swap/dump flexibility
> that we just gave initial install. I'll bring this up within the team.
The (partial) workaround I tried was:
1. create a ZFS BE in an existing pool that has enough space
2 lumount the BE, edit the vfstab to use the
I will look into this. I don't know why it would have failed.
Lori
Rainer Orth wrote:
Lori Alt <[EMAIL PROTECTED]> writes:
use of swap/dump zvols? If your existing swap/dump slice
is contiguous with your root pool, you can grow the root
pool into that space (using format to merge the sl
Alan Burlison wrote:
> Lori Alt wrote:
>
>> What if you turned slice 1 into a pool (a new one), migrated your BE
>> into it,
>> then grow that pool to soak up the space in the slices that follow
>> it? You might
>> still need to save some stuff elsewhere while you're doing the
>> transition.
Lori Alt wrote:
> What if you turned slice 1 into a pool (a new one), migrated your BE
> into it,
> then grow that pool to soak up the space in the slices that follow it?
> You might
> still need to save some stuff elsewhere while you're doing the transition.
Doesn't work, because LU wants to
Alan Burlison wrote:
Lori Alt wrote:
In designing the changes to the install software, we had to
decide whether to be all things to all people or make some
default choices. Being all things to all people makes the
interface a lot more complicated and takes a lot more
engineering effort (
Lori Alt <[EMAIL PROTECTED]> writes:
> use of swap/dump zvols? If your existing swap/dump slice
> is contiguous with your root pool, you can grow the root
> pool into that space (using format to merge the slices.
> A reboot or re-import of the pool will cause it to grow into
> the newly-available
Lori Alt wrote:
> In designing the changes to the install software, we had to
> decide whether to be all things to all people or make some
> default choices. Being all things to all people makes the
> interface a lot more complicated and takes a lot more
> engineering effort (we'd still be develo
[EMAIL PROTECTED] wrote:
> Just make sure you use dumpadm to point to valid dump device and
> this setup should work fine. Please let us know if it doesn't.
Yep, works fine.
> The ZFS strategy behind automatically creating separate swap and
> dump devices including the following:
>
> o Eliminat
Alan Burlison wrote:
[EMAIL PROTECTED] wrote:
ZFS doesn't swap to a slice in build 92. In this build, a ZFS root
environment requires separate ZFS volumes for swap and dump devices.
The ZFS boot/install project and information trail starts here:
http://opensolaris.org/os/community/zfs/b
[EMAIL PROTECTED] wrote:
> Alan,
>
> Just make sure you use dumpadm to point to valid dump device and
> this setup should work fine. Please let us know if it doesn't.
>
> The ZFS strategy behind automatically creating separate swap and
> dump devices including the following:
>
> o Eliminates the
Alan,
Just make sure you use dumpadm to point to valid dump device and
this setup should work fine. Please let us know if it doesn't.
The ZFS strategy behind automatically creating separate swap and
dump devices including the following:
o Eliminates the need to create separate slices
o Enables u
[EMAIL PROTECTED] wrote:
> ZFS doesn't swap to a slice in build 92. In this build, a ZFS root
> environment requires separate ZFS volumes for swap and dump devices.
>
> The ZFS boot/install project and information trail starts here:
>
> http://opensolaris.org/os/community/zfs/boot/
Is this goin
Hi Alan,
ZFS doesn't swap to a slice in build 92. In this build, a ZFS root
environment requires separate ZFS volumes for swap and dump devices.
The ZFS boot/install project and information trail starts here:
http://opensolaris.org/os/community/zfs/boot/
Cindy
Alan Burlison wrote:
> I'm up
I'm upgrading my B92 UFS-boot system to ZFS root using Live Upgrade. It
appears to work fine so far, but I'm wondering why it allocates a ZFS
filesystem for swap when I already have a dedicated swap slice.
Shouldn't it just use any existing swap slice rather than creating a ZFS
one?
--
Alan
22 matches
Mail list logo
