Sunday Sep 28, 2008

First reboot after install of w2100z

Okay, so I got this configuration:

# zpool list
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
rpool    68G  7.18G  60.8G    10%  ONLINE  -
# zpool iostat -v
                 capacity     operations    bandwidth
pool           used  avail   read  write   read  write
------------  -----  -----  -----  -----  -----  -----
rpool         7.18G  60.8G     31     14   814K   528K
  mirror      7.18G  60.8G     31     14   814K   528K
    c1t0d0s0      -      -     12      8   509K   530K
    c1t1d0s0      -      -     13      8   510K   530K
------------  -----  -----  -----  -----  -----  -----

But I don't want a mirror, I want space!

This should work, but it doesn't:

# zpool detach rpool c1t1d0s0
# zpool iostat -v
               capacity     operations    bandwidth
pool         used  avail   read  write   read  write
----------  -----  -----  -----  -----  -----  -----
rpool       7.18G  60.8G      8      6   367K   383K
  c1t0d0s0  7.18G  60.8G      8      6   367K   383K
----------  -----  -----  -----  -----  -----  -----

# zpool add rpool c1t1d0s0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c1t1d0s0 overlaps with /dev/dsk/c1t1d0s2
# zpool add -f rpool c1t1d0s0
cannot add to 'rpool': root pool can not have multiple vdevs or separate logs

Ahh, I should have done some light reading, from ZFS Troubleshooting Guide:

You cannot use a RAID-Z configuration for a root pool. Only single-disk pools or pools with mirrored disks are supported.

I was thinking of reinstalling, but no, I'll go with two different pools. By the way, I understand the need for redundancy, but I'd prefer more spindles here.

# zpool create tank c1t1d0s0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c1t1d0s0 overlaps with /dev/dsk/c1t1d0s2
# zpool create -f tank c1t1d0s0
# zpool iostat -v
               capacity     operations    bandwidth
pool         used  avail   read  write   read  write
----------  -----  -----  -----  -----  -----  -----
rpool       7.18G  60.8G      5      4   246K   255K
  c1t0d0s0  7.18G  60.8G      5      4   246K   255K
----------  -----  -----  -----  -----  -----  -----
tank        73.5K  68.0G      0      9  18.3K   165K
  c1t1d0s0  73.5K  68.0G      0      9  18.3K   165K
----------  -----  -----  -----  -----  -----  -----

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Time to update my w2100z

When I last configured my w2100z, it wasn't possible to have a ZFS root. And I did some funky stuff playing around with it. My current configuration (I have 2 drives, which I think should be 72G):

       0. c1t0d0 
          /pci@5,0/pci1022,7450@4/pci108e,534d@4,1/sd@0,0
Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm     524 - 3134       20.00GB    (2611/0/0)  41945715
  1       swap    wu       1 -  523        4.01GB    (523/0/0)    8401995
  2     backup    wm       0 - 8913       68.28GB    (8914/0/0) 143203410
  3 unassigned    wm    3135 - 5745       20.00GB    (2611/0/0)  41945715
  4 unassigned    wm    5746 - 8356       20.00GB    (2611/0/0)  41945715
  5 unassigned    wm       0               0         (0/0/0)            0
  6 unassigned    wm       0               0         (0/0/0)            0
  7       home    wm    8357 - 8913        4.27GB    (557/0/0)    8948205
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0
       1. c1t1d0 
          /pci@5,0/pci1022,7450@4/pci108e,534d@4,1/sd@1,0
Part      Tag    Flag     Cylinders        Size            Blocks
  0      stand    wm       1 - 4466       34.21GB    (4466/0/0)  71746290
  1      stand    wm    4467 - 8932       34.21GB    (4466/0/0)  71746290
  2     backup    wu       0 - 8932       68.43GB    (8933/0/0) 143508645
  3 unassigned    wm       0               0         (0/0/0)            0
  4 unassigned    wm       0               0         (0/0/0)            0
  5 unassigned    wm       0               0         (0/0/0)            0
  6 unassigned    wm       0               0         (0/0/0)            0
  7 unassigned    wm       0               0         (0/0/0)            0
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0

I've shamelessly munged together output from different format commands. Anyway, the first drive has several available partitions for Live Update and grabbing in case of need. The second drive has two partitions used for ZFS.

This configuration is very flexible for doing updates. I can have several boot partitions on the root drive and I never have to worry about the data on my ZFS pool:

[root@warlock snv99]> zpool list zoo
NAME   SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
zoo     68G  51.5G  16.5G    75%  ONLINE  -
[root@warlock snv99]> zpool iostat -v
               capacity     operations    bandwidth
pool         used  avail   read  write   read  write
----------  -----  -----  -----  -----  -----  -----
zoo         51.5G  16.5G      0      1  21.9K  60.8K
  c1t1d0s0  33.6G   381M      0      0  7.31K  12.0K
  c1t1d0s1  17.9G  16.1G      0      1  14.6K  48.8K
----------  -----  -----  -----  -----  -----  -----

But I think I want to live more on the edge. I'm looking to get a more modern build on warlock:

[root@warlock snv99]> uname -a
SunOS warlock 5.11 snv_85 i86pc i386 i86pc

So, I'm going to back everything up onto an attached USB drive, and nuke the entire system.

Back in a bit

Since warlock is headless, the first task is to build an install DVD which has a modified menu.lst for grub - see Getting a Solaris bootable DVD for headless x86es.

While I'm doing that, I'm going to back up my system. I need the contents of /etc, my punchin configuration (a Sun VPN tool), my Sun Ray server configuration, and my homedirs. The rest I could probably care less about or already have saved off.

Also, I'm pretty ruthless, once I decide I don't need something, I will delete it. That gives me a better idea of how how much I still have to backup. And no, I'm not talking system stuff. Take for example here where I delete some ISO images:

[th199096@warlock isos]> df -h .
Filesystem             size   used  avail capacity  Mounted on
zoo/isos                67G    29G    16G    65%    /zoo/isos
[th199096@warlock x86]>	rm -rf snv7\* snv8\* snv90/ snv97
[th199096@warlock x86]>	df -h .
Filesystem             size   used  avail capacity  Mounted on
zoo/isos                67G    12G    33G    27%    /zoo/isos

You may not be comfortable with this approach, but once you reinstall it is gone anyway.

Cleaned out, the ISO is booting in a VirtualBox on my WinXP desktop, so I'm signing off here....


Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily
About

tdh

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today