Axelle Apvrille
2009-Jul-24 11:52 UTC
[zfs-discuss] Soon out of space (after upgrade to 2009.06)
Hi, I have upgraded from to 2008.11 to 2009.06. The upgrade process created a new boot environment (named opensolaris-1 in my case), but I am now getting out of space in my ZFS pool. So, can I safely erase the old boot environment, and if so will that get me back the disk space I need ? BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris R - 7.57G static 2009-01-03 13:18 opensolaris-1 N / 3.20G static 2009-07-20 22:38 As you see there, my new BE has 3G only, I probably need more. zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 41.8G 6.24G 1.42G /a/rpool rpool/ROOT 10.4G 6.24G 18K legacy rpool/ROOT/opensolaris 7.18G 6.24G 6.75G / rpool/ROOT/opensolaris-1 3.20G 6.24G 7.36G / rpool/dump 895M 6.24G 895M - rpool/export 28.2G 6.24G 19K /export rpool/export/home 28.2G 6.24G 654M /export/home rpool/export/home/axelle 27.5G 6.24G 27.4G /export/home/axelle rpool/swap 895M 7.03G 88.3M - Of course, I don''t want to erase any critical file or data. However, I do not wish to boot 2008.11 any longer as 2009.06 is working. Thanks Axelle -- This message posted from opensolaris.org
Jean-Noël Mattern
2009-Jul-24 13:04 UTC
[zfs-discuss] Soon out of space (after upgrade to 2009.06)
Axelle, You can safely run "beadm destroy opensolaris" if everything''s allright with your new opensolaris-1 boot env. You will get back your space (something around 7.18 GB). There''s something strang with the mountpoint of rpool which should be /rpool and not /a/rpool, maybe you''ll have to fix this with "zfs set mountpoint=/rpool rpool". Be sure before to do that that you back up what''s in /rpool, and restore it after having the mountpoint changed! Jnm. -- Axelle Apvrille a ?crit :> Hi, > I have upgraded from to 2008.11 to 2009.06. The upgrade process created a new boot environment (named opensolaris-1 in my case), but I am now getting out of space in my ZFS pool. So, can I safely erase the old boot environment, and if so will that get me back the disk space I need ? > > BE Active Mountpoint Space Policy Created > -- ------ ---------- ----- ------ ------- > opensolaris R - 7.57G static 2009-01-03 13:18 > opensolaris-1 N / 3.20G static 2009-07-20 22:38 > > As you see there, my new BE has 3G only, I probably need more. > > zfs list > NAME USED AVAIL REFER MOUNTPOINT > rpool 41.8G 6.24G 1.42G /a/rpool > rpool/ROOT 10.4G 6.24G 18K legacy > rpool/ROOT/opensolaris 7.18G 6.24G 6.75G / > rpool/ROOT/opensolaris-1 3.20G 6.24G 7.36G / > rpool/dump 895M 6.24G 895M - > rpool/export 28.2G 6.24G 19K /export > rpool/export/home 28.2G 6.24G 654M /export/home > rpool/export/home/axelle 27.5G 6.24G 27.4G /export/home/axelle > rpool/swap 895M 7.03G 88.3M - > > Of course, I don''t want to erase any critical file or data. However, I do not wish to boot 2008.11 any longer as 2009.06 is working. > > Thanks > Axelle >
In general, questions about beadm and related tools should be sent or at least cross-posted to install-discuss at opensolaris.org. Lori On 07/24/09 07:04, Jean-No?l Mattern wrote:> Axelle, > > You can safely run "beadm destroy opensolaris" if everything''s > allright with your new opensolaris-1 boot env. > > You will get back your space (something around 7.18 GB). > > There''s something strang with the mountpoint of rpool which should be > /rpool and not /a/rpool, maybe you''ll have to fix this with "zfs set > mountpoint=/rpool rpool". Be sure before to do that that you back up > what''s in /rpool, and restore it after having the mountpoint changed! > > Jnm. > > -- > > Axelle Apvrille a ?crit : >> Hi, >> I have upgraded from to 2008.11 to 2009.06. The upgrade process >> created a new boot environment (named opensolaris-1 in my case), but >> I am now getting out of space in my ZFS pool. So, can I safely erase >> the old boot environment, and if so will that get me back the disk >> space I need ? >> >> BE Active Mountpoint Space Policy Created >> -- ------ ---------- ----- ------ ------- >> opensolaris R - 7.57G static 2009-01-03 13:18 >> opensolaris-1 N / 3.20G static 2009-07-20 22:38 >> As you see there, my new BE has 3G only, I probably need more. >> >> zfs list >> NAME USED AVAIL REFER MOUNTPOINT >> rpool 41.8G 6.24G 1.42G /a/rpool >> rpool/ROOT 10.4G 6.24G 18K legacy >> rpool/ROOT/opensolaris 7.18G 6.24G 6.75G / >> rpool/ROOT/opensolaris-1 3.20G 6.24G 7.36G / >> rpool/dump 895M 6.24G 895M - >> rpool/export 28.2G 6.24G 19K /export >> rpool/export/home 28.2G 6.24G 654M /export/home >> rpool/export/home/axelle 27.5G 6.24G 27.4G /export/home/axelle >> rpool/swap 895M 7.03G 88.3M - >> >> Of course, I don''t want to erase any critical file or data. However, >> I do not wish to boot 2008.11 any longer as 2009.06 is working. >> >> Thanks >> Axelle >> > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Axelle Apvrille
2009-Jul-24 20:08 UTC
[zfs-discuss] Soon out of space (after upgrade to 2009.06)
Ok -- thanks for your reply. I just wonder what''s in those 7 G, if a 3G pool is enough... ? Why has it grown so much ? I think I do not understand exactly the relationship between BE and the ZFS pools: if I destroy the BE, that doesn''t destroy the data, does it ? it puts back the content of rpool/ROOT/opensolaris in rpool/ROOT/opensolaris-1 and thus there is a single pool with approximately 10G ? Best regards, Axelle PS. Now cross-posting to install. :) -- This message posted from opensolaris.org