system:vicki_debian_lenny_to_squeeze
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| system:vicki_debian_lenny_to_squeeze [2012-02-14T13:40:57+0000] – added autostart and confirmation bits michael_paoli | system:vicki_debian_lenny_to_squeeze [2013-02-17T20:00:48+0000] (current) – typo/wordo fix michael_paoli | ||
|---|---|---|---|
| Line 28: | Line 28: | ||
| ===== draft/ | ===== draft/ | ||
| < | < | ||
| - | # hostname --fqdn; pwd -P; expand -t 2 < 0001_a_general_plan_or_outline | + | # hostname --fqdn; pwd -P; expand -t 2 < 0010_a_general_plan_or_outline |
| + | vicki.sf-lug.com | ||
| + | / | ||
| SF-LUG & BALUG: System OS upgrades *soon*(?) - volunteer(s)? | SF-LUG & BALUG: System OS upgrades *soon*(?) - volunteer(s)? | ||
| Line 76: | Line 78: | ||
| | | ||
| o install Debian 6.0.4 amd64, using beginning area(s) of disks | o install Debian 6.0.4 amd64, using beginning area(s) of disks | ||
| - | | + | |
| | | ||
| - | | + | |
| used for /boot and LVM2 respectively) | used for /boot and LVM2 respectively) | ||
| | | ||
| Line 114: | Line 116: | ||
| references: | references: | ||
| http:// | http:// | ||
| + | # | ||
| </ | </ | ||
| Line 143: | Line 146: | ||
| ===== disk layout, etc. details: ===== | ===== disk layout, etc. details: ===== | ||
| < | < | ||
| - | # hostname --fqdn; pwd -P; more 000[23]* | expand -t 2 | + | # hostname --fqdn; pwd -P; more 00[23]* | expand -t 2 |
| vicki.sf-lug.com | vicki.sf-lug.com | ||
| / | / | ||
| :::::::::::::: | :::::::::::::: | ||
| - | 0002_vicki-pre-disk-analysis | + | 0020_vicki-pre-disk-analysis |
| :::::::::::::: | :::::::::::::: | ||
| //hard drive partitions, we have: | //hard drive partitions, we have: | ||
| Line 244: | Line 247: | ||
| //excepting extended partition, all logical and non-zero length primary | //excepting extended partition, all logical and non-zero length primary | ||
| - | // | + | // |
| //raid1 devices: | //raid1 devices: | ||
| # mdadm --verbose --examine --scan | # mdadm --verbose --examine --scan | ||
| Line 305: | Line 308: | ||
| // | // | ||
| :::::::::::::: | :::::::::::::: | ||
| - | 0003_vicki_initial_disk_prep | + | 0030_vicki_initial_disk_prep |
| :::::::::::::: | :::::::::::::: | ||
| //before: | //before: | ||
| Line 337: | Line 340: | ||
| [[ip_addresses|IP Addresses]] | [[ip_addresses|IP Addresses]] | ||
| < | < | ||
| - | # hostname --fqdn; pwd -P; expand < 0005_networking | + | # hostname --fqdn; pwd -P; expand < 0050_networking |
| vicki.sf-lug.com | vicki.sf-lug.com | ||
| / | / | ||
| Line 418: | Line 421: | ||
| dns-search sf-lug.com | dns-search sf-lug.com | ||
| $ | $ | ||
| - | # | + | # |
| </ | </ | ||
| ===== xen --> qemu-kvm (specific example sflug): ===== | ===== xen --> qemu-kvm (specific example sflug): ===== | ||
| < | < | ||
| - | # hostname --fqdn; pwd -P; expand -t 2 < 0006_vicki_sflug_xen2qemu-kvm | + | # hostname --fqdn; pwd -P; expand -t 2 < 0060_vicki_sflug_xen2qemu-kvm |
| vicki.sf-lug.com | vicki.sf-lug.com | ||
| / | / | ||
| Line 431: | Line 434: | ||
| o sflug is Debian GNU/Linux 5.0.9 i386 (excepting some slight bits that | o sflug is Debian GNU/Linux 5.0.9 i386 (excepting some slight bits that | ||
| may predate that - e.g. some existing low-level bits quite | may predate that - e.g. some existing low-level bits quite | ||
| - | | + | |
| nevertheless, | nevertheless, | ||
| i386) | i386) | ||
| Line 450: | Line 453: | ||
| filesystem, as applicable) | filesystem, as applicable) | ||
| o UUIDs should be unique, so we adjust accordingly | o UUIDs should be unique, so we adjust accordingly | ||
| - | o use e2fstune | + | o use tune2fs |
| o use mkswap to recreate target swap | o use mkswap to recreate target swap | ||
| o use blkid to determine UUID and label(s) of the above targets | o use blkid to determine UUID and label(s) of the above targets | ||
| Line 477: | Line 480: | ||
| --disk path=/ | --disk path=/ | ||
| --wait=-1 | --wait=-1 | ||
| - | boot the (virtual) guest from CD into graphical recovery | + | boot the (virtual) guest from CD into Graphical rescue |
| ... | ... | ||
| Device to use as root file system: /dev/sda1 | Device to use as root file system: /dev/sda1 | ||
| Line 538: | Line 541: | ||
| # virsh autostart sflug | # virsh autostart sflug | ||
| o shutdown guest(s), reboot host, check that all properly comes up | o shutdown guest(s), reboot host, check that all properly comes up | ||
| - | # | + | # |
| + | </ | ||
| + | ===== vicki host install/" | ||
| + | < | ||
| + | # hostname --fqdn; pwd -P; expand -t 2 < 0070_vicki_upgrade_steps | ||
| + | vicki.sf-lug.com | ||
| + | / | ||
| + | vicki upgrade key steps (outline of general procedure - fair bit of | ||
| + | detail, but skipping details of many of the more obvious/ | ||
| + | |||
| + | (remaining) pre steps: | ||
| + | o remount /boot ro | ||
| + | o backup /boot data | ||
| + | o backup MBR (440 bytes) | ||
| + | o shutdown VM guests | ||
| + | o attach KVM | ||
| + | o shutdown vicki | ||
| + | |||
| + | install(/ | ||
| + | o attach bootable USB image: debian-6.0.4-amd64-CD-1.iso | ||
| + | o boot USB | ||
| + | o Advanced options | ||
| + | o Graphical expert install | ||
| + | o ... | ||
| + | o Configure locales, add all en_US* locales | ||
| + | o default locale: en_us.UTF-8 | ||
| + | o ... | ||
| + | o Load installer components from CD, include: | ||
| + | o cfdisk-udeb | ||
| + | o choose-mirror | ||
| + | o multipath | ||
| + | o openssh | ||
| + | o parted-udeb | ||
| + | o partman-reiserfs | ||
| + | o reiserfs-modules | ||
| + | o Configure the network | ||
| + | o Auto-configure network with DHCP: | ||
| + | o no | ||
| + | o IP address: 208.96.15.250 | ||
| + | o Netmask: 255.255.255.248 | ||
| + | o Gateway: 208.96.15.249 | ||
| + | o Name server addresses: 216.93.160.11 216.93.160.16 | ||
| + | o Hostname: vicki | ||
| + | o Domain name: sf-lug.com | ||
| + | o Set up users and passwords | ||
| + | o Allow login as root: yes (will change that later) | ||
| + | o Create a normal user account now?: No | ||
| + | o Configure the clock | ||
| + | o ... | ||
| + | o Pacific | ||
| + | o Partition disks | ||
| + | o Manual | ||
| + | ONLY TOUCH PARTITIONS #1 AND #2 ON EACH DISK, DO NOT RECREATE OR MOVE | ||
| + | THEM, THEY MUST REMAIN EXACTLY WHERE THEY ARE AND THE OTHER | ||
| + | PARTITIONS TOTALLY UNTOUCHED | ||
| + | o Configure software RAID | ||
| + | o Keep current partition layout and conigure RAID?: Yes | ||
| + | o Create MD device | ||
| + | o RAID1 | ||
| + | o Number of active devices for the RAID1 array: 2 | ||
| + | o Number of spare devices for the RAID1 array: 0 | ||
| + | o select partition 1 from both disks | ||
| + | o Keep current partition layout and conigure RAID?: Yes | ||
| + | o Create MD device | ||
| + | o RAID1 | ||
| + | o Number of active devices for the RAID1 array: 2 | ||
| + | o Number of spare devices for the RAID1 array: 0 | ||
| + | o select partition 2 from both disks | ||
| + | o Keep current partition layout and conigure RAID?: Yes | ||
| + | o Finish | ||
| + | o RAID1 device #0 #1 | ||
| + | o Ext3 | ||
| + | o /boot | ||
| + | o vicki-boot | ||
| + | o RAID1 device #1 #1 | ||
| + | o physical volume for LVM | ||
| + | o Configure the Logical Volume Manager | ||
| + | o Write the changes to disks and configure LVM?: Yes | ||
| + | o Create volume group | ||
| + | o Volume group name: vicki | ||
| + | o /dev/md1 | ||
| + | o Create logical volume | ||
| + | logical volume name & size | ||
| + | root / 1G | ||
| + | usr 2G | ||
| + | var 4G | ||
| + | home 2G | ||
| + | (we'll add swap later, not now: | ||
| + | swap1 512M | ||
| + | swap2 512M | ||
| + | swap3 512M | ||
| + | swap4 512M | ||
| + | ) | ||
| + | o Partition disks | ||
| + | LVM mount fs type | ||
| + | root / ext3 | ||
| + | usr /usr ext3 | ||
| + | var /var ext3 | ||
| + | home /home ext3 | ||
| + | o RAID1 device #0 #1 | ||
| + | o Ext3 | ||
| + | o /boot | ||
| + | o vicki-boot | ||
| + | o Finish partitioning and write changes to disk | ||
| + | (continue without swap) | ||
| + | o Install base system | ||
| + | after that, and before kernel, etc.: | ||
| + | |||
| + | ID " | ||
| + | At this point, target filesystems are mounted on/under /target, including | ||
| + | / | ||
| + | there yet). Here's where we start UID/GID reconciliation and alignment | ||
| + | and merging in, etc. of IDs from " | ||
| + | merge/ | ||
| + | |||
| + | activate and use console session on tty2 (Ctrl+Alt+F2) | ||
| + | |||
| + | start additional md (mdadm) devices, e.g.: | ||
| + | ~ # mdadm --assemble /dev/md2 / | ||
| + | ~ # mdadm --assemble /dev/md3 / | ||
| + | ~ # mdadm --assemble /dev/md4 / | ||
| + | ~ # mdadm --assemble /dev/md5 / | ||
| + | ~ # mdadm --assemble /dev/md6 / | ||
| + | ~ # mdadm --assemble /dev/md7 / | ||
| + | ~ # mdadm --assemble /dev/md8 / | ||
| + | ~ # mdadm --assemble /dev/md9 / | ||
| + | ~ # mdadm --assemble /dev/md10 / | ||
| + | |||
| + | Scan for volume groups: | ||
| + | ~ # vgscan | ||
| + | and activate: | ||
| + | ~ # vgchange -a y vg00 | ||
| + | ~ # vgchange -a y vg-local | ||
| + | ~ # vgchange -a y vg-sflug | ||
| + | ~ # vgchange -a y vg-balug | ||
| + | |||
| + | mount " | ||
| + | and while we're at it, ssh keys: | ||
| + | ~ # mkdir /tmp/mnt | ||
| + | ~ # mount -o ro / | ||
| + | ~ # (umask 077 && mkdir / | ||
| + | ~ # (cd / | ||
| + | ~ # (cd / | ||
| + | unmount " | ||
| + | ~ # umount /tmp/mnt && rmdir /tmp/mnt | ||
| + | |||
| + | chroot into target we're building: | ||
| + | ~ # cd / && exec chroot /target | ||
| + | optionally give us more " | ||
| + | # cd / && exec /bin/bash --posix --login | ||
| + | bash-4.1# PS1='# ' | ||
| + | # set -o vi; FCEDIT=vi VISUAL=vi EDITOR=vi export FCEDIT VISUAL EDITOR | ||
| + | |||
| + | mount /proc filesystem: | ||
| + | # mount /proc | ||
| + | |||
| + | VERY CAREFULLY merge in ID information from / | ||
| + | corresponding /etc/* files: | ||
| + | # vipw | ||
| + | # pwconv | ||
| + | # vipw -s | ||
| + | # vigr | ||
| + | # grpconv | ||
| + | # vigr -s | ||
| + | etc. as needed | ||
| + | |||
| + | and NOTE ANY CHANGES WE'LL NEED TO MAKE, | ||
| + | e.g.: | ||
| + | o any changes on NEW filesystem(s) and/or | ||
| + | o any changes on OLD filesystem(s) | ||
| + | At last dry run check on 2012-02-25, the following issues were found, | ||
| + | and their recommended actions: | ||
| + | login/UID conflicts/ | ||
| + | |||
| + | libuuid | ||
| + | new UID/GID on target | ||
| + | adjust any old data before allowing import, multichown IDspec: | ||
| + | 107, | ||
| + | |||
| + | 100 | ||
| + | uid conflict (libuuid vs. old Debian-exim) | ||
| + | change Debian-exim to available <1000 UID | ||
| + | adjust any old data before allowing import, | ||
| + | multichown IDspec (replacing Debian-exim with new target UID, e.g. 125): | ||
| + | 100,125 | ||
| + | |||
| + | group/GID conflicts/ | ||
| + | |||
| + | libuuid | ||
| + | new GID on target: 101 | ||
| + | adjust any old data before allowing import, | ||
| + | ,,107,101 | ||
| + | |||
| + | crontab | ||
| + | new GID on target: 102 | ||
| + | adjust any old data before allowing import, | ||
| + | ,,101,102 | ||
| + | |||
| + | 102 | ||
| + | gid conflict (vs. old Debian-exim) | ||
| + | change Debian-exim to available <1000 UID | ||
| + | adjust any old data before allowing import, | ||
| + | ,,102,125 | ||
| + | |||
| + | umount /proc filesystem from within chroot and exit chroot: | ||
| + | # umount /proc && exit | ||
| + | |||
| + | o continue with installation (kernel, etc.) | ||
| + | o include non-free (in case we need it for, e.g. firmware) | ||
| + | o Software selection | ||
| + | o Choose software to install: | ||
| + | | ||
| + | x SSH server | ||
| + | x Standard system utilities | ||
| + | | ||
| + | o Is the system clock set to UTC?: Yes | ||
| + | ... | ||
| + | reboot to single user | ||
| + | empty contents of /tmp | ||
| + | edit /etc/fstab to use tmpfs for tmp: | ||
| + | tmpfs /tmp tmpfs nosuid, | ||
| + | mount /tmp | ||
| + | recopy our " | ||
| + | reboot | ||
| + | |||
| + | Should be able to login via ssh as " | ||
| + | verify that, and if okay, disable root login via ssh | ||
| + | |||
| + | start additional md (mdadm) devices, e.g.: | ||
| + | # mdadm --assemble /dev/md2 / | ||
| + | # mdadm --assemble /dev/md3 / | ||
| + | # mdadm --assemble /dev/md4 / | ||
| + | # mdadm --assemble /dev/md5 / | ||
| + | # mdadm --assemble /dev/md6 / | ||
| + | # mdadm --assemble /dev/md7 / | ||
| + | # mdadm --assemble /dev/md8 / | ||
| + | # mdadm --assemble /dev/md9 / | ||
| + | # mdadm --assemble /dev/md10 / | ||
| + | add them to / | ||
| + | # / | ||
| + | ... and apply those changes | ||
| + | |||
| + | mount our CD image and configure into apt | ||
| + | |||
| + | install: | ||
| + | sudo libvirt-bin libvirt-doc virtinst virt-viewer qemu-kvm ed nvi | ||
| + | reconfigure network using br0 | ||
| + | |||
| + | convert sflug from Xen to qemu-kvm and configure to autostart | ||
| + | |||
| + | change line in / | ||
| + | loop | ||
| + | to: | ||
| + | loop max_loop=256 | ||
| + | reboot vicki, confirm all comes up as expected | ||
| + | |||
| + | time permitting, work on IMPI | ||
| + | |||
| + | remainder can be handled remotely | ||
| + | # | ||
| </ | </ | ||
| ===== checklist/ | ===== checklist/ | ||
| * laptop(s) - Michael Paoli | * laptop(s) - Michael Paoli | ||
| - | * Ethernet cables - Michael Paoli | + | * Ethernet cables |
| * 10/100/1000 Mbit Ethernet switch - Michael Paoli | * 10/100/1000 Mbit Ethernet switch - Michael Paoli | ||
| - | * " | + | * " |
| - | * portable power strip - Michael Paoli | + | * portable power strips |
| * off-line accessible copies of reference documentation, | * off-line accessible copies of reference documentation, | ||
| * existing root passwords | * existing root passwords | ||
| Line 555: | Line 817: | ||
| * Debian GNU/Linux 6.0.4 " | * Debian GNU/Linux 6.0.4 " | ||
| * Debian GNU/Linux 6.0.4 " | * Debian GNU/Linux 6.0.4 " | ||
| - | ===== to do: ===== | + | |
| - | *prepare more general outline | + | ===== procedure " |
| - | *save needed | + | * sf-lug.com: disable its IP: 208.96.15.251 currently and from restart (not needed for sf-lug.com, and highly useful |
| - | *checklist/outline | + | * Michael Paoli linux laptop - configure for network: |
| - | *xen --> qemu-kvm | + | * down dhcp server, repoint dhcp server to config. for Servepath |
| - | *work out, test, and document | + | * reconfig br0: # ifconfig br0 208.96.15.253 netmask 255.255.255.248 broadcast 208.96.15.255 up |
| + | * # route add default gw 208.96.15.249 | ||
| + | * DNS: 216.93.160.11 216.93.160.16 | ||
| + | * restart dhcp server | ||
| + | * connect: | ||
| + | * Gig switch: Internet, vicki, Michael Paoli linux laptop, Linksys " | ||
| + | * Linksys Ethernet ports 1-5 - additional laptop(s) (drive/ | ||
| + | * (www.)sf-lug.com - prepare to have services temporarily on Michael Paoli' | ||
| + | * have command set, but don't yet hit enter: # ifconfig br0:1 208.96.15.252 netmask 255.255.255.248 broadcast 208.96.15.255 up | ||
| + | * bring down sflug domU, and once down, hit enter on above command | ||
| + | * test connectivity/ | ||
| + | * shutdown the balug VM | ||
| + | * continue with vicki " | ||
| + | * before bringing sflug VM back up on Internet, on Michael Paoli' | ||
| + | * # ifconfig br0:1 down | ||
| + | ===== vicki " | ||
| + | * 2012-02-27 initial main phase of vicki being " | ||
| + | * 2012-03-01 completed UID/GID alignments - " | ||
| + | ===== balug VM upgraded to Debian GNU/Linux 6.0.4 ===== | ||
| + | * 2012-03-04--2012-03-05 balug VM was upgraded, remnant cleanup tasks completed relatively shortly thereafter | ||
| + | * balug VM log bits made available here: [[http:// | ||
| + | ===== sflug VM upgrade | ||
| + | * sflug VM log bits made available here: [[http:// | ||
| + | * upgrade to be done [[http:// | ||
| + | * will be upgrading/ | ||
| + | * **backup(s)** - since [www.]sf-lug.com is (generally) " | ||
| + | * from host (vicki), sflug' | ||
| + | * we can take an LV snapshot of that LV, create backup copy of snapshot, then release the snapshot, | ||
| + | * though that doesn' | ||
| + | * it does give us fully recoverable point-in-time capture of the guest' | ||
| + | * note that otherwise taking a copy of live filesystem | ||
| + | * note also other methods could be used to ensure recoverable copy, e.g. by creating a mirror, " | ||
| + | * note also we need to pay due attention/care regarding UUIDs and such to avoid problems, as this LVM snapshot method will introduce some duplication of UUIDs, but note, however, in our scenario that is //mostly// a non-issue, as: | ||
| + | * from the host there are separate and unique LVs, and for the most part host wouldn' | ||
| + | * we won't present both " | ||
| + | * also, these backups are " | ||
| + | * note also this is separate/independent | ||
| + | * doing the backup - here's part of what doing the " | ||
| + | < | ||
| + | //I show my comments on lines starting with // | ||
| + | //I don't show all output of all commands (mostly reduced for brevity/ | ||
| + | //from sflug (guest), we have relatively simplistic filesystem and swap setup, | ||
| + | //one " | ||
| + | //with partition for root (/) filesystem, and swap | ||
| + | # sfdisk -uS -l | ||
| + | |||
| + | Disk /dev/sda: 1435 cylinders, 255 heads, 63 sectors/ | ||
| + | Units = sectors of 512 bytes, counting from 0 | ||
| + | |||
| + | | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | / | ||
| + | # | ||
| + | //and to confirm a bit - ignoring virtual filesystems, | ||
| + | # mount -t notmpfs, | ||
| + | /dev/sda1 on / type ext3 (rw, | ||
| + | # awk ' | ||
| + | UUID=792a4837-91bc-4b36-bce7-a5a4208845bf / ext3 errors=remount-ro 0 1 #/ | ||
| + | # blkid /dev/sda1 | ||
| + | /dev/sda1: UUID=" | ||
| + | # cat / | ||
| + | Filename | ||
| + | / | ||
| + | # awk ' | ||
| + | UUID=e326206f-55a6-4fbb-8c81-62f8dfb30753 none swap sw 0 0 #/dev/sda2 LABEL=swap | ||
| + | # blkid /dev/sda2 | ||
| + | /dev/sda2: TYPE=" | ||
| + | # | ||
| + | //so, quite simple there and no surprises. | ||
| + | # hostname | ||
| + | vicki | ||
| + | # virsh list --all | ||
| + | Id Name | ||
| + | ---------------------------------- | ||
| + | 2 sflug running | ||
| + | 26 balug running | ||
| + | |||
| + | # virsh dumpxml sflug | fgrep '< | ||
| + | <source dev='/ | ||
| + | # | ||
| + | //so, the storage for the sflug VM is on / | ||
| + | //how much space used and free (and PE size) for that VG? | ||
| + | # vgdisplay / | ||
| + | PE Size 4.00 MiB | ||
| + | Total PE 6904 | ||
| + | Alloc PE / Size 2941 / 11.49 GiB | ||
| + | Free PE / Size 3963 / 15.48 GiB | ||
| + | # | ||
| + | //so, we can see that a fair bit less than half of the VG is used, | ||
| + | //thus we know we've got ample room to complete our backup, | ||
| + | //and also for our snapshot LV to be present; | ||
| + | //snapshot LV doesn' | ||
| + | //as it essentially only tracks changed data, | ||
| + | //and since we'll do this backup relatively quickly, | ||
| + | //and the sflug host won't be changing lots of data nor quickly at that time anyway, | ||
| + | //we don't need much space for the snapshot. | ||
| + | //So, let's do a good test run of our procedure: | ||
| + | //we peek at LV names in the VG, to avoid any accidental name collision: | ||
| + | # ls / | ||
| + | sda sflug-disk-BACKUP | ||
| + | # | ||
| + | //we examine size of our source LV: | ||
| + | # lvdisplay / | ||
| + | Current LE | ||
| + | # | ||
| + | //we create our target LV, | ||
| + | // | ||
| + | //as that's codename of the " | ||
| + | //and less likely to cause confusion (e.g. backup, which backup, when, of what?) | ||
| + | # lvcreate -l 2816 -n sda-lenny vg-sflug | ||
| + | Logical volume " | ||
| + | # | ||
| + | //we check on free PEs in our VG - we'll use them all for our snapshot (probably excessive), | ||
| + | //but we only need them for a quite short while anyway, | ||
| + | //so not an issue to be a bit excessive here for a quite short while anyway. | ||
| + | //we reexamine our free PEs in the VG: | ||
| + | # vgdisplay / | ||
| + | Free PE / Size 1147 / 4.48 GiB | ||
| + | # | ||
| + | //we use them all for our snapshot LV: | ||
| + | # lvcreate -l 1147 -n sda-snapshot -s / | ||
| + | Logical volume " | ||
| + | //I include use of time below, just to see how long it takes (dd also happens to provide similar information) | ||
| + | //and also, especially when operating as superuser (root), we want to be sure our commands are correct, | ||
| + | //Unix, and mostly likewise Linux, tends to presume one knows what one is doing, | ||
| + | //and probably doubly (or more) so for superuser, | ||
| + | //so carefully triple-check the command(s) before viciously striking the < | ||
| + | //(says me ;-) - has saved my butt on more than one occasion) | ||
| + | //here we want to be particularly careful with where we're writing our data to, | ||
| + | //what we remove, | ||
| + | //and also that we in fact pick our correct data source | ||
| + | # time dd if=/ | ||
| + | 2816+0 records in | ||
| + | 2816+0 records out | ||
| + | 11811160064 bytes (12 GB) copied, 424.946 s, 27.8 MB/s | ||
| + | |||
| + | real 7m4.957s | ||
| + | user 0m0.016s | ||
| + | sys | ||
| + | //a bit over 7 minutes - from a point-in-time snapshot, recoverable, | ||
| + | //had we done that instead with source of the live rw mounted sda (well, containing sda1), | ||
| + | //what we'd have had instead in our target data would have been an inconsistent mess with no guarantees of recoverability | ||
| + | //and out of curiosity, just before removing it, | ||
| + | //I peek at our snapshot to see how much space it has actually used: | ||
| + | # lvdisplay / | ||
| + | Current LE | ||
| + | COW-table LE | ||
| + | Allocated to snapshot | ||
| + | //as we can see, almost none (0.16%) | ||
| + | //and removing our snapshot: | ||
| + | # lvremove -f / | ||
| + | Logical volume " | ||
| + | # | ||
| + | //removing the snapshot is important - if it's left around ("too long") and runs out of room, I/O on the LVs stops | ||
| + | //(that can then be corrected by extending the snapshot LV, or removing it) | ||
| + | //pretty much the same LV snapshot techniques are often used for live database (DB) backups, e.g.: | ||
| + | //put the relevant database files/ | ||
| + | //(done within the DB, and in many cases involves more than one which must be done together as a set), | ||
| + | //snapshot them (as set), take database (or those files/ | ||
| + | //proceed to next set, etc., | ||
| + | //and also release each snapshot after it (or its set) has completed being backed up. | ||
| + | //so, as exercise, we'll check the recoverability of our backup, | ||
| + | //since it's just one journaled filesystem (and swap, that we don't care about the swap data), | ||
| + | //fairly simple to test (we won't do this test when we do our backup "for real" - we know it works, | ||
| + | // | ||
| + | //And to note first, we're going to bend our UUID " | ||
| + | //as here we're going to give host peek into the guest' | ||
| + | //as we only let it see one instance of this UUID, | ||
| + | //as the other duplicate UUIDs are within the partitions of / | ||
| + | //which we won't be having the host access (certainly at least not at the same time!) | ||
| + | //from our partition information earlier from the guest (we could also examine it from the host), | ||
| + | //we know how to construct a loop device to access just the first partition within our LV copy: | ||
| + | # losetup -o `expr 512 '*' 63` --sizelimit `expr 512 ' | ||
| + | / | ||
| + | # | ||
| + | //does it match what we expect? | ||
| + | # blkid / | ||
| + | /dev/loop0: UUID=" | ||
| + | # | ||
| + | //yes ... journaled filesystem, so, manner in which we copied it should be quite recoverable, | ||
| + | //but rather than just try to mount it (which may replay journal and do relatively light checks), | ||
| + | // | ||
| + | // | ||
| + | //to replay - but that should be about it). | ||
| + | # fsck.ext3 -f / | ||
| + | e2fsck 1.41.12 (17-May-2010) | ||
| + | /dev/loop0: recovering journal | ||
| + | Clearing orphaned inode 278547 (uid=0, gid=1, mode=0100700, | ||
| + | Pass 1: Checking inodes, blocks, and sizes | ||
| + | Pass 2: Checking directory structure | ||
| + | Pass 3: Checking directory connectivity | ||
| + | Pass 4: Checking reference counts | ||
| + | Pass 5: Checking group summary information | ||
| + | |||
| + | /dev/loop0: ***** FILE SYSTEM WAS MODIFIED ***** | ||
| + | /dev/loop0: 28306/ | ||
| + | # | ||
| + | //and as we'd expect, quite " | ||
| + | //some bit(s) like Clearing orphaned inode or similar, may be expected, | ||
| + | //e.g. if snapshot happens, and there are unlinked open files at the time, | ||
| + | //then those files no longer exist in any directory, | ||
| + | //but their inode (and storage, if any) hasn't yet been freed, | ||
| + | //while that's normal for Unix/Linux if a PID still has the files open, | ||
| + | // | ||
| + | //so that bit if housekeeping on the filesystem is still to be done (which would | ||
| + | //normally happen rather quickly on live mounted filesystem after last PID having the unlinked | ||
| + | //file open, closed the file (explicitly, | ||
| + | //we could do more with that filesystem (e.g. testing, etc.) if we wished at this point, | ||
| + | //but that more than suffices for our testing here, so time to free up that loop device: | ||
| + | # losetup -d / | ||
| + | # | ||
| + | </file> | ||
| + | * **incorporating " | ||
| + | * from earlier similar upgrade done on balug qemu-kvm VM guest on same host, encountered **problem with reboot - namely upgrade procedure produced a flawed / | ||
| + | |||
| + | < | ||
| + | installation " | ||
| + | http:// | ||
| + | namely reboot failed - kernel couldn' | ||
| + | upon investigation, | ||
| + | lines in / | ||
| + | then able to proceed | ||
| + | </ | ||
| + | * **relevant Debian documentation**: | ||
| + | * [[http:// | ||
| + | * **especially: | ||
| + | * will do pre-upgrade steps in advance as feasible, have done the following: | ||
| + | * 4.1.1\\ output of:\\ # dpkg_--get-selections ' | ||
| + | * 4.1.6 checked package splashy not installed | ||
| + | * 4.2 - should be good on no 3rd party packages, etc., system has been updated to the latest point release of lenny (5.0.10). | ||
| + | * 4.2.1 checked good: No packages are scheduled to be installed, removed, or upgraded. | ||
| + | * 4.2.2 good (/ | ||
| + | * 4.2.3:\\ looks good: # dpkg --audit\\ dpkg -l looks quite good, used: # dpkg -l | grep -v '^ii '\\ dpkg --get-selections ' | ||
| + | * 4.2.4 proposed-updates not in / | ||
| + | * 4.2.5 - presumably not an issue (doesn' | ||
| + | * **done** (main upgrade proper sequence, and immediately preceding steps): | ||
| + | * did LV snapshot backup, from host (vicki) (target created earlier; also, this was set up to execute via at(1) at 5:40 P.M. on the day of the upgrade - 20 minutes prior to start of our upgrade maintenance window; and in earlier | ||
| + | * # lvcreate -l 1147 -n sda-snapshot -s / | ||
| + | * # time dd if=/ | ||
| + | * # lvremove -f / | ||
| + | * and here's what that script that was executed looks like, and its output: | ||
| + | < | ||
| + | # hostname; pwd -P; cat bkup; echo; cat bkup.out | ||
| + | vicki | ||
| + | / | ||
| + | #!/bin/sh | ||
| + | set -e | ||
| + | umask 077 | ||
| + | cd / | ||
| + | at 1740 << \__EOT__ | ||
| + | set -e | ||
| + | umask 077 | ||
| + | cd / | ||
| + | exec >> bkup.out 2>& | ||
| + | echo start `date -Iseconds` | ||
| + | [ -b / | ||
| + | lvcreate -l 1147 -n sda-snapshot -s / | ||
| + | time dd if=/ | ||
| + | lvremove -f / | ||
| + | } | ||
| + | echo end `date -Iseconds` | ||
| + | __EOT__ | ||
| + | |||
| + | start 2012-03-14T17: | ||
| + | Logical volume " | ||
| + | 2816+0 records in | ||
| + | 2816+0 records out | ||
| + | 11811160064 bytes (12 GB) copied, 421.079 s, 28.0 MB/s | ||
| + | 0.01user 34.83system 7: | ||
| + | 23068824inputs+23068680outputs (1major+1242minor)pagefaults 0swaps | ||
| + | Logical volume " | ||
| + | end 2012-03-14T17: | ||
| + | # | ||
| + | </ | ||
| + | * present Debian GNU/Linux 6.0.4 " | ||
| + | * on guest, scan SCSI devices, create mount point (if not present), update /etc/fstab, and mount it: | ||
| + | * # (for tmp in / | ||
| + | * # (umask 022 && mkdir / | ||
| + | * Even though we told the host to present the device to guest as sdc, it showed up on guest as sdb, so we went with that: | ||
| + | * add to / | ||
| + | * # mount / | ||
| + | * 4.3 - continue per documentation\\ add new cdrom ISO to / | ||
| + | * looking now at the above, and checking shell history, had actually intended to use / | ||
| + | * # ln -s / | ||
| + | * ... | ||
| + | * 4.4.5 **before** first reboot, inspected / | ||
| + | * inspected legacy grub, and grub2 configurations - grub looked fine, tweaked grub2 - mostly via / | ||
| + | * ... | ||
| + | * we essentially completed through step 4.6.3, " | ||
| + | * we also checked both web server and DNS server both on the host and up and running and operational as expected. | ||
| + | * **and done(!)** - these bits were completed later, but not later than 2012-03-17: | ||
| + | * went through and completed our various clean-up tasks: | ||
| + | * reviewed configurations - in the interests of time (and uptime), some of the configurations where we had local modifications, | ||
| + | * init / rc stuff - we didn't earlier get the advantages of the newer faster start-up system - some legacy/ | ||
| + | * 4.7 (the part before 4.7.1) | ||
| + | * steps starting at and beyond step 4.8 | ||
| + | * saved script output from most of the upgrade process - reviewed that for any potentially security sensitive bits, and as there weren' | ||
| + | * high-level (human written (with some machine assist) and intended for human consumption) log file for the system is available at:\\ [[http:// | ||
| + | * did full virtual power reboot test (did reboot tests 2012-03-14, but not with full virtual power down and back up again with guest), ensured that guest comes up fine with no need for any console input being provided | ||
| + | * and (documentation bits - didn't really need to refer to or use this particular document with/for our upgrade) also if/ | ||
system/vicki_debian_lenny_to_squeeze.1329226857.txt.bz2 · Last modified: 2012-02-14T13:40:57+0000 by michael_paoli