root slice always forced to be s0 (overwrites)
Bug #158326 reported by
NicoDVB
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Nexenta Operating System |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
I tried to install Nexenta 1.0b1t3 on a partitition wher I had previously installeded Nevada 75.
The partition contained 3 slices:
s0 (12 GB) /
s1 (4GB) swap
s3(32GB) assigned but unmounted
During the installation of Nexenta I chose s3 as root (zfs)
and s1 as swap, paying attention not to touch s0;
guess what? Nexenta used s0 as /, formatting and destroying
my Nevada!
Revision history for this message
| Tim Spriggs (tim-tajinc) wrote | #1 |
Revision history for this message
| Tim Spriggs (tim-tajinc) wrote | #2 |
To post a comment you must log in.
It turns out that the manual partitioning in later releases of the installer is disabled. However I think this should turn into an RFE for better handling of syspool creation. In specific, I think that the entire disk should be used by default and a swap volume on the syspool should be created/used instead of a swap slice.
There have been a number of complaints about lack of a manual partitioner in the IRC channel because people do not want to use an entire disk.
Any ideas/comments on how this should work?