[opensuse] Tiny /boot Partition
OSE 11.3 (Fresh Install) When I first installed this about six weeks back, I wanted to create a boot partition sufficiently large but could not make the installer budge beyond the tiny default of 68MB. Frustrated, I went ahead and now it has returned to bite me. I not only cannot have multiple kernel versions but there is not even enought space to upgrade the kernel. Proposed solution: I added a second virtual disk (this is running under ESXi 4.1) and will copy the old boot partition contents to the new one, update the /boot/grub/menu.lst, modify the fstab and remove the active partition marker from the old /dev/sda1 boot partition and make the new /dev/sdb1 active. Will this work? Another alternative I can also do is to create another OSE guest and copy the non OS partitions over. Obviously, I prefer the first option unless I overlooked something. Here is what /dev/sda looks like: Filesystem Size Used Avail Use% Mounted on /dev/mapper/system-root 20G 4.6G 15G 25% / devtmpfs 1003M 168K 1003M 1% /dev tmpfs 1005M 4.0K 1005M 1% /dev/shm /dev/sda1 68M 54M 12M 83% /boot /dev/mapper/system-home 79G 21G 55G 28% /home /dev/mapper/system-local 130G 67G 57G 54% /local /dev/mapper/system-tmp 9.9G 151M 9.2G 2% /tmp /dev/mapper/system-var 9.9G 521M 8.9G 6% /var ux-ose:~ # fdisk -l /dev/sda Disk /dev/sda: 274.9 GB, 274877906944 bytes 255 heads, 63 sectors/track, 33418 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bd81d Device Boot Start End Blocks Id System /dev/sda1 * 1 10 71680 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 10 33419 268362752 8e Linux LVM ux-ose:~ # fdisk -l /dev/sdb Disk /dev/sdb: 536 MB, 536870912 bytes 64 heads, 32 sectors/track, 512 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa7dcbfcc Device Boot Start End Blocks Id System /dev/sdb1 1 512 524272 83 Linux Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010-09-19 01:41, Lucky Leavell wrote:
OSE 11.3 (Fresh Install)
When I first installed this about six weeks back, I wanted to create a boot partition sufficiently large but could not make the installer budge beyond the tiny default of 68MB. Frustrated, I went ahead and now it has returned to bite me. I not only cannot have multiple kernel versions but there is not even enought space to upgrade the kernel.
Clear space. My /boot has only 20 MB used.
Proposed solution: I added a second virtual disk (this is running under ESXi 4.1) and will copy the old boot partition contents to the new one, update the /boot/grub/menu.lst, modify the fstab and remove the active partition marker from the old /dev/sda1 boot partition and make the new /dev/sdb1 active.
Will this work?
No. No because the marked bootable thing can not go from one disk to another, it has to be in the same disk as where the MBR is. You can, however, have the "small" boot chain load another grub and boot in another disk, and do it fast (0 seconds). -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))
On Sun, 19 Sep 2010, Carlos E. R. wrote:
On 2010-09-19 01:41, Lucky Leavell wrote:
OSE 11.3 (Fresh Install)
When I first installed this about six weeks back, I wanted to create a boot partition sufficiently large but could not make the installer budge beyond the tiny default of 68MB. Frustrated, I went ahead and now it has returned to bite me. I not only cannot have multiple kernel versions but there is not even enought space to upgrade the kernel.
Clear space. My /boot has only 20 MB used.
Here is my /boot directory: -rw------- 1 root root 512 2010-07-31 12:17 backup_mbr lrwxrwxrwx 1 root root 1 2010-07-31 11:53 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 14:57 boot.readme -rw-r--r-- 1 root root 111540 2010-07-05 09:27 config-2.6.34-12-default -rw-r--r-- 1 root root 111090 2010-07-05 10:21 config-2.6.34-12-desktop drwxr-xr-x 2 root root 1024 2010-08-09 22:01 grub/ lrwxrwxrwx 1 root root 24 2010-07-31 12:16 initrd -> initrd-2.6.34-12-default -rw-r--r-- 1 root root 10724163 2010-07-31 12:16 initrd-2.6.34-12-default -rw-r--r-- 1 root root 10735715 2010-07-31 12:17 initrd-2.6.34-12-desktop drwx------ 2 root root 12288 2010-07-31 11:45 lost+found/ -rw-r--r-- 1 root root 418816 2010-08-09 22:01 message -rw-r--r-- 1 root root 166755 2010-07-05 09:37 symsets-2.6.34-12-default.tar.gz -rw-r--r-- 1 root root 165874 2010-07-05 10:34 symsets-2.6.34-12-desktop.tar.gz -rw-r--r-- 1 root root 163896 2010-07-05 09:36 symsets-2.6.34-12-xen.tar.gz -rw-r--r-- 1 root root 530688 2010-07-05 09:36 symtypes-2.6.34-12-default.gz -rw-r--r-- 1 root root 527668 2010-07-05 10:32 symtypes-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 519257 2010-07-05 09:35 symtypes-2.6.34-12-xen.gz -rw-r--r-- 1 root root 188006 2010-07-05 09:28 symvers-2.6.34-12-default.gz -rw-r--r-- 1 root root 187496 2010-07-05 10:23 symvers-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 1939139 2010-07-05 09:09 System.map-2.6.34-12-default -rw-r--r-- 1 root root 1996824 2010-07-05 10:02 System.map-2.6.34-12-desktop -rw-r--r-- 1 root root 4562810 2010-07-05 09:26 vmlinux-2.6.34-12-default.gz -rw-r--r-- 1 root root 4751262 2010-07-05 10:21 vmlinux-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 4105121 2010-07-05 09:29 vmlinux-2.6.34-12-xen.gz lrwxrwxrwx 1 root root 25 2010-07-31 11:59 vmlinuz -> vmlinuz-2.6.34-12-default -rw-r--r-- 1 root root 3927296 2010-07-05 09:09 vmlinuz-2.6.34-12-default -rw-r--r-- 1 root root 4098208 2010-07-05 10:02 vmlinuz-2.6.34-12-desktop Obviously, I can get rid of the xen stuff. Why does it install both the default and desktop kernels? Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/09/18 21:14 (GMT-0400) Lucky Leavell composed:
Lucky Leavell wrote:
OSE 11.3 (Fresh Install)
When I first installed this about six weeks back, I wanted to create a boot partition sufficiently large but could not make the installer budge beyond the tiny default of 68MB. Frustrated, I went ahead and now it has returned to bite me. I not only cannot have multiple kernel versions but there is not even enought space to upgrade the kernel.
Here is my /boot directory:
-rw------- 1 root root 512 2010-07-31 12:17 backup_mbr lrwxrwxrwx 1 root root 1 2010-07-31 11:53 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 14:57 boot.readme -rw-r--r-- 1 root root 111540 2010-07-05 09:27 config-2.6.34-12-default -rw-r--r-- 1 root root 111090 2010-07-05 10:21 config-2.6.34-12-desktop drwxr-xr-x 2 root root 1024 2010-08-09 22:01 grub/ lrwxrwxrwx 1 root root 24 2010-07-31 12:16 initrd -> initrd-2.6.34-12-default -rw-r--r-- 1 root root 10724163 2010-07-31 12:16 initrd-2.6.34-12-default -rw-r--r-- 1 root root 10735715 2010-07-31 12:17 initrd-2.6.34-12-desktop
Each of those is nearly twice the size of mine (32bit on Intel CPU & chipset). The pair combine to use about 30% of total /boot space. Are everyone's 64bit initrds that much bigger than 32 bit?
drwx------ 2 root root 12288 2010-07-31 11:45 lost+found/ -rw-r--r-- 1 root root 418816 2010-08-09 22:01 message -rw-r--r-- 1 root root 166755 2010-07-05 09:37 symsets-2.6.34-12-default.tar.gz -rw-r--r-- 1 root root 165874 2010-07-05 10:34 symsets-2.6.34-12-desktop.tar.gz -rw-r--r-- 1 root root 163896 2010-07-05 09:36 symsets-2.6.34-12-xen.tar.gz -rw-r--r-- 1 root root 530688 2010-07-05 09:36 symtypes-2.6.34-12-default.gz -rw-r--r-- 1 root root 527668 2010-07-05 10:32 symtypes-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 519257 2010-07-05 09:35 symtypes-2.6.34-12-xen.gz -rw-r--r-- 1 root root 188006 2010-07-05 09:28 symvers-2.6.34-12-default.gz -rw-r--r-- 1 root root 187496 2010-07-05 10:23 symvers-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 1939139 2010-07-05 09:09 System.map-2.6.34-12-default -rw-r--r-- 1 root root 1996824 2010-07-05 10:02 System.map-2.6.34-12-desktop -rw-r--r-- 1 root root 4562810 2010-07-05 09:26 vmlinux-2.6.34-12-default.gz -rw-r--r-- 1 root root 4751262 2010-07-05 10:21 vmlinux-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 4105121 2010-07-05 09:29 vmlinux-2.6.34-12-xen.gz lrwxrwxrwx 1 root root 25 2010-07-31 11:59 vmlinuz -> vmlinuz-2.6.34-12-default -rw-r--r-- 1 root root 3927296 2010-07-05 09:09 vmlinuz-2.6.34-12-default -rw-r--r-- 1 root root 4098208 2010-07-05 10:02 vmlinuz-2.6.34-12-desktop
Obviously, I can get rid of the xen stuff. Why does it install both the default and desktop kernels?
IIRC it's fallout from that last round of openSUSE dev kernel renaming that no one's bothered to fix. It infrequently bothers anyone that it happens, and provides some safety measure in case one or the other doesn't actually work. If you're running a primarily desktop system, zypper rm the default kernel. Otherwise, zypper rm the desktop kernel while you're removing xen. What filesystem is your /boot? If not EXT2, there's space wasted on needless journaling. You could copy everything off, umount, mkfs.ext2 -bs1024 -I128, mount, copy everything back, and see probably a significant space increase. You could also resize smaller first / and then larger /boot if your partitions support resizing. I only use EXT2 & EXT3, both of which do. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 18 Sep 2010, Felix Miata wrote:
On 2010/09/18 21:14 (GMT-0400) Lucky Leavell composed:
Lucky Leavell wrote:
OSE 11.3 (Fresh Install)
When I first installed this about six weeks back, I wanted to create a boot partition sufficiently large but could not make the installer budge beyond the tiny default of 68MB. Frustrated, I went ahead and now it has returned to bite me. I not only cannot have multiple kernel versions but there is not even enought space to upgrade the kernel.
Here is my /boot directory:
-rw------- 1 root root 512 2010-07-31 12:17 backup_mbr lrwxrwxrwx 1 root root 1 2010-07-31 11:53 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 14:57 boot.readme -rw-r--r-- 1 root root 111540 2010-07-05 09:27 config-2.6.34-12-default -rw-r--r-- 1 root root 111090 2010-07-05 10:21 config-2.6.34-12-desktop drwxr-xr-x 2 root root 1024 2010-08-09 22:01 grub/ lrwxrwxrwx 1 root root 24 2010-07-31 12:16 initrd -> initrd-2.6.34-12-default -rw-r--r-- 1 root root 10724163 2010-07-31 12:16 initrd-2.6.34-12-default -rw-r--r-- 1 root root 10735715 2010-07-31 12:17 initrd-2.6.34-12-desktop
Each of those is nearly twice the size of mine (32bit on Intel CPU & chipset). The pair combine to use about 30% of total /boot space.
Are everyone's 64bit initrds that much bigger than 32 bit?
drwx------ 2 root root 12288 2010-07-31 11:45 lost+found/ -rw-r--r-- 1 root root 418816 2010-08-09 22:01 message -rw-r--r-- 1 root root 166755 2010-07-05 09:37 symsets-2.6.34-12-default.tar.gz -rw-r--r-- 1 root root 165874 2010-07-05 10:34 symsets-2.6.34-12-desktop.tar.gz -rw-r--r-- 1 root root 163896 2010-07-05 09:36 symsets-2.6.34-12-xen.tar.gz -rw-r--r-- 1 root root 530688 2010-07-05 09:36 symtypes-2.6.34-12-default.gz -rw-r--r-- 1 root root 527668 2010-07-05 10:32 symtypes-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 519257 2010-07-05 09:35 symtypes-2.6.34-12-xen.gz -rw-r--r-- 1 root root 188006 2010-07-05 09:28 symvers-2.6.34-12-default.gz -rw-r--r-- 1 root root 187496 2010-07-05 10:23 symvers-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 1939139 2010-07-05 09:09 System.map-2.6.34-12-default -rw-r--r-- 1 root root 1996824 2010-07-05 10:02 System.map-2.6.34-12-desktop -rw-r--r-- 1 root root 4562810 2010-07-05 09:26 vmlinux-2.6.34-12-default.gz -rw-r--r-- 1 root root 4751262 2010-07-05 10:21 vmlinux-2.6.34-12-desktop.gz -rw-r--r-- 1 root root 4105121 2010-07-05 09:29 vmlinux-2.6.34-12-xen.gz lrwxrwxrwx 1 root root 25 2010-07-31 11:59 vmlinuz -> vmlinuz-2.6.34-12-default -rw-r--r-- 1 root root 3927296 2010-07-05 09:09 vmlinuz-2.6.34-12-default -rw-r--r-- 1 root root 4098208 2010-07-05 10:02 vmlinuz-2.6.34-12-desktop
Obviously, I can get rid of the xen stuff. Why does it install both the default and desktop kernels?
The only xen stuff is kernel-xen-devel, not the full xen kernel which is a dependency for kernel-syms. I am not sure if I needs kernel syms.
IIRC it's fallout from that last round of openSUSE dev kernel renaming that no one's bothered to fix. It infrequently bothers anyone that it happens, and provides some safety measure in case one or the other doesn't actually work.
If you're running a primarily desktop system, zypper rm the default kernel. Otherwise, zypper rm the desktop kernel while you're removing xen.
Actually, since this is running under ESXi, most access is via SSH, not the desktop. The default runlevel is 3.
What filesystem is your /boot? If not EXT2, there's space wasted on needless journaling. You could copy everything off, umount, mkfs.ext2 -bs1024 -I128, mount, copy everything back, and see probably a significant space increase.
I might try that. It is ext4: /dev/sda1 /boot ext4 acl,user_xattr 1 2 I did reduce the reserved block percentage to 1% and reclaimed almost 3MB. (tune2fs -m 1 /dev/sda1)
You could also resize smaller first / and then larger /boot if your partitions support resizing. I only use EXT2 & EXT3, both of which do.
I might try this or simply reinstall by creating another OSE11.3 VM and copy (rsync) /home. I have ample disk space to do this. You mentioned RHEL easrlier. My "day" job is as an admin on RHEL systems and this is one of the few things I like RHEL better, namely it by default saves several kernel versions. Obviously, I still choose SuSE at home and every place I have the choice.
-- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/09/19 07:18 (GMT-0400) Lucky Leavell composed:
On Sat, 18 Sep 2010, Felix Miata wrote:
What filesystem is your /boot? If not EXT2, there's space wasted on needless journaling. You could copy everything off, umount, mkfs.ext2 -bs1024 -I128, mount, copy everything back, and see probably a significant space increase.
I might try that.
It is ext4: /dev/sda1 /boot ext4 acl,user_xattr 1 2
Devoting any space for acl or user_xattr on a boot partition seems equally useless as journaling. I wonder if they eat up a significant amount of space on a 68M partition? Hmmm, probably not significant. I just created a 208813 block test partition to match my /boot, formatted ext4, mounted with acl,user_xattr, copied all of /boot, and wound up with only 3504 fewer blocks (1.67%) free on the ext4 copy.
I did reduce the reserved block percentage to 1% and reclaimed almost 3MB. (tune2fs -m 1 /dev/sda1)
You mentioned RHEL easrlier. My "day" job is as an admin on RHEL systems and this is one of the few things I like RHEL better, namely it by default saves several kernel versions.
SUSE doesn't by default, but it can optionally using multiversion in /etc/zypp/zypp.conf, and not just for kernels. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 19/09/10 08:44, Felix Miata escribió:
On 2010/09/19 07:18 (GMT-0400) Lucky Leavell composed:
On Sat, 18 Sep 2010, Felix Miata wrote:
What filesystem is your /boot? If not EXT2, there's space wasted on needless journaling. You could copy everything off, umount, mkfs.ext2 -bs1024 -I128, mount, copy everything back, and see probably a significant space increase.
I might try that.
It is ext4: /dev/sda1 /boot ext4 acl,user_xattr 1 2
Devoting any space for acl or user_xattr on a boot partition seems equally useless as journaling.
You can disable journaling in ext4 with 11.3 kernels... tune2fs -O ^has_journal ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010-09-19 05:39, Felix Miata wrote:
On 2010/09/18 21:14 (GMT-0400) Lucky Leavell composed:
-rw-r--r-- 1 root root 10724163 2010-07-31 12:16 initrd-2.6.34-12-default -rw-r--r-- 1 root root 10735715 2010-07-31 12:17 initrd-2.6.34-12-desktop
Each of those is nearly twice the size of mine (32bit on Intel CPU & chipset). The pair combine to use about 30% of total /boot space.
Are everyone's 64bit initrds that much bigger than 32 bit?
No. I have both 32 and 64 systems on the same machine, and initrd is about 6 Mb on both. -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))
On Saturday 18 September 2010 22:39:01 Felix Miata wrote:
On 2010/09/18 21:14 (GMT-0400) Lucky Leavell composed: ...
Here is my /boot directory:
-rw------- 1 root root 512 2010-07-31 12:17 backup_mbr lrwxrwxrwx 1 root root 1 2010-07-31 11:53 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 14:57 boot.readme -rw-r--r-- 1 root root 111540 2010-07-05 09:27 config-2.6.34-12-default -rw-r--r-- 1 root root 111090 2010-07-05 10:21 config-2.6.34-12-desktop drwxr-xr-x 2 root root 1024 2010-08-09 22:01 grub/ lrwxrwxrwx 1 root root 24 2010-07-31 12:16 initrd -> initrd-2.6.34-12-default -rw-r--r-- 1 root root 10724163 2010-07-31 12:16 initrd-2.6.34-12-default -rw-r--r-- 1 root root 10735715 2010-07-31 12:17 initrd-2.6.34-12-desktop
Each of those is nearly twice the size of mine (32bit on Intel CPU & chipset). The pair combine to use about 30% of total /boot space.
Are everyone's 64bit initrds that much bigger than 32 bit?
It seems so: drwxr-xr-x 3 root root 4096 2010-09-13 22:45 ./ drwxr-xr-x 25 root root 4096 2010-09-18 04:32 ../ -rw------- 1 root root 512 2010-08-06 21:03 backup_mbr lrwxrwxrwx 1 root root 1 2010-08-06 20:54 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 13:57 boot.readme -rw-r--r-- 1 root root 115775 2010-09-04 01:55 config-2.6.36-rc3-10-desktop drwxr-xr-x 2 root root 4096 2010-09-04 18:24 grub/ lrwxrwxrwx 1 root root 28 2010-09-04 18:24 initrd -> initrd-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 11112236 2010-09-04 18:24 initrd-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 418816 2010-08-06 21:03 message -rw-r--r-- 1 root root 172759 2010-09-04 02:10 symsets-2.6.36-rc3-10-default.tar.gz -rw-r--r-- 1 root root 172179 2010-09-04 02:03 symsets-2.6.36-rc3-10-desktop.tar.gz -rw-r--r-- 1 root root 167878 2010-09-04 02:06 symsets-2.6.36-rc3-10-xen.tar.gz -rw-r--r-- 1 root root 548868 2010-09-04 02:09 symtypes-2.6.36-rc3-10-default.gz -rw-r--r-- 1 root root 548745 2010-09-04 02:01 symtypes-2.6.36-rc3-10-desktop.gz -rw-r--r-- 1 root root 536946 2010-09-04 02:05 symtypes-2.6.36-rc3-10-xen.gz -rw-r--r-- 1 root root 195626 2010-09-04 01:57 symvers-2.6.36-rc3-10-desktop.gz -rw-r--r-- 1 root root 2057614 2010-09-04 01:42 System.map-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 4611073 2010-09-04 02:01 vmlinux-2.6.36-rc3-10-default.gz -rw-r--r-- 1 root root 4871507 2010-09-04 01:55 vmlinux-2.6.36-rc3-10-desktop.gz -rw-r--r-- 1 root root 4241317 2010-09-04 01:59 vmlinux-2.6.36-rc3-10-xen.gz lrwxrwxrwx 1 root root 29 2010-09-04 18:23 vmlinuz -> vmlinuz-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 4198192 2010-09-04 01:42 vmlinuz-2.6.36-rc3-10-desktop There is only one kernel that one can boot, all other is development stuff installed to compile kernel modules. I complained once why ksyms pulls all other kernels, but explanation was that it must be that way. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 19 Sep 2010, Rajko M. wrote:
On Saturday 18 September 2010 22:39:01 Felix Miata wrote:
On 2010/09/18 21:14 (GMT-0400) Lucky Leavell composed: ...
Here is my /boot directory:
-rw------- 1 root root 512 2010-07-31 12:17 backup_mbr lrwxrwxrwx 1 root root 1 2010-07-31 11:53 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 14:57 boot.readme -rw-r--r-- 1 root root 111540 2010-07-05 09:27 config-2.6.34-12-default -rw-r--r-- 1 root root 111090 2010-07-05 10:21 config-2.6.34-12-desktop drwxr-xr-x 2 root root 1024 2010-08-09 22:01 grub/ lrwxrwxrwx 1 root root 24 2010-07-31 12:16 initrd -> initrd-2.6.34-12-default -rw-r--r-- 1 root root 10724163 2010-07-31 12:16 initrd-2.6.34-12-default -rw-r--r-- 1 root root 10735715 2010-07-31 12:17 initrd-2.6.34-12-desktop
Each of those is nearly twice the size of mine (32bit on Intel CPU & chipset). The pair combine to use about 30% of total /boot space.
Are everyone's 64bit initrds that much bigger than 32 bit?
It seems so:
drwxr-xr-x 3 root root 4096 2010-09-13 22:45 ./ drwxr-xr-x 25 root root 4096 2010-09-18 04:32 ../ -rw------- 1 root root 512 2010-08-06 21:03 backup_mbr lrwxrwxrwx 1 root root 1 2010-08-06 20:54 boot -> ./ -rw-r--r-- 1 root root 1236 2010-07-01 13:57 boot.readme -rw-r--r-- 1 root root 115775 2010-09-04 01:55 config-2.6.36-rc3-10-desktop drwxr-xr-x 2 root root 4096 2010-09-04 18:24 grub/ lrwxrwxrwx 1 root root 28 2010-09-04 18:24 initrd -> initrd-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 11112236 2010-09-04 18:24 initrd-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 418816 2010-08-06 21:03 message -rw-r--r-- 1 root root 172759 2010-09-04 02:10 symsets-2.6.36-rc3-10-default.tar.gz -rw-r--r-- 1 root root 172179 2010-09-04 02:03 symsets-2.6.36-rc3-10-desktop.tar.gz -rw-r--r-- 1 root root 167878 2010-09-04 02:06 symsets-2.6.36-rc3-10-xen.tar.gz -rw-r--r-- 1 root root 548868 2010-09-04 02:09 symtypes-2.6.36-rc3-10-default.gz -rw-r--r-- 1 root root 548745 2010-09-04 02:01 symtypes-2.6.36-rc3-10-desktop.gz -rw-r--r-- 1 root root 536946 2010-09-04 02:05 symtypes-2.6.36-rc3-10-xen.gz -rw-r--r-- 1 root root 195626 2010-09-04 01:57 symvers-2.6.36-rc3-10-desktop.gz -rw-r--r-- 1 root root 2057614 2010-09-04 01:42 System.map-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 4611073 2010-09-04 02:01 vmlinux-2.6.36-rc3-10-default.gz -rw-r--r-- 1 root root 4871507 2010-09-04 01:55 vmlinux-2.6.36-rc3-10-desktop.gz -rw-r--r-- 1 root root 4241317 2010-09-04 01:59 vmlinux-2.6.36-rc3-10-xen.gz lrwxrwxrwx 1 root root 29 2010-09-04 18:23 vmlinuz -> vmlinuz-2.6.36-rc3-10-desktop -rw-r--r-- 1 root root 4198192 2010-09-04 01:42 vmlinuz-2.6.36-rc3-10-desktop
There is only one kernel that one can boot, all other is development stuff installed to compile kernel modules. I complained once why ksyms pulls all other kernels, but explanation was that it must be that way.
One of the choices offered is to remove kernel-xen-devel anyway, breaking the dependencies. Would that break my system or should I leave it be? I don't do much development but have compiled stuff that required the development stuff. Alternatively, what if I removed the xen stuff to another filesystem and soft linked it back since it apparently is not used in booting the OS? Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 September 2010 12:11:53 Lucky Leavell wrote:
Alternatively, what if I removed the xen stuff to another filesystem and soft linked it back since it apparently is not used in booting the OS?
You can do that. I just created /usr/local/boot which is on the same partition (file system) and moved there: backup_mbr boot.readme symsets-2.6.36-rc3-10-default.tar.gz symsets-2.6.36-rc3-10-desktop.tar.gz symsets-2.6.36-rc3-10-xen.tar.gz symtypes-2.6.36-rc3-10-default.gz symtypes-2.6.36-rc3-10-desktop.gz symtypes-2.6.36-rc3-10-xen.gz symvers-2.6.36-rc3-10-desktop.gz vmlinux-2.6.36-rc3-10-default.gz vmlinux-2.6.36-rc3-10-desktop.gz vmlinux-2.6.36-rc3-10-xen.gz That is 16 MB files. I was in a /boot directory, and run: lndir /usr/local/boot which created symlinks of each file in /usr/local/boot in /boot . For compilation this should be fine and boot is now 17 MB, plus /boot/grub 185 KB. You can use instead / of your system partition. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 19 Sep 2010, Rajko M. wrote:
On Sunday 19 September 2010 12:11:53 Lucky Leavell wrote:
Alternatively, what if I removed the xen stuff to another filesystem and soft linked it back since it apparently is not used in booting the OS?
You can do that.
I just created /usr/local/boot which is on the same partition (file system) and moved there: backup_mbr boot.readme symsets-2.6.36-rc3-10-default.tar.gz symsets-2.6.36-rc3-10-desktop.tar.gz symsets-2.6.36-rc3-10-xen.tar.gz symtypes-2.6.36-rc3-10-default.gz symtypes-2.6.36-rc3-10-desktop.gz symtypes-2.6.36-rc3-10-xen.gz symvers-2.6.36-rc3-10-desktop.gz vmlinux-2.6.36-rc3-10-default.gz vmlinux-2.6.36-rc3-10-desktop.gz vmlinux-2.6.36-rc3-10-xen.gz
That is 16 MB files.
I was in a /boot directory, and run: lndir /usr/local/boot which created symlinks of each file in /usr/local/boot in /boot . For compilation this should be fine and boot is now 17 MB, plus /boot/grub 185 KB.
You can use instead / of your system partition.
I see two issues, at least on my system: 1. /boot and /root are on separate partitions 2. root and all other partitions except /boot are LVM. Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 September 2010 16:33:25 Lucky Leavell wrote:
I see two issues, at least on my system:
1. /boot and /root are on separate partitions 2. root and all other partitions except /boot are LVM.
The LVM part is problem. It would be nice if you can resize LVM partition. I still did not find enough incentive to use LVM, so I can't help you with that more then Google. The other option is to put in computer another disk and install small Linux installation with X and some old fashioned window manager that will be rescue and boot system. Disadvantage is that you will have to update both when kernel update is due. Third is to backup /home and start from scratch. Create partitions before you start installation, for instance from Live CD, and then run installation. In any case it will be interesting to know what exactly what you did with current installation. I didn't have problems with installer, but I don't use separate boot, and LVM. If it did not allow you to make partition bigger then 68M then you should file a bug report. When I recall that my first 2 hard disks were 80MB :) -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 19 Sep 2010, Rajko M. wrote:
On Sunday 19 September 2010 16:33:25 Lucky Leavell wrote:
I see two issues, at least on my system:
1. /boot and /root are on separate partitions 2. root and all other partitions except /boot are LVM.
The LVM part is problem. It would be nice if you can resize LVM partition. I still did not find enough incentive to use LVM, so I can't help you with that more then Google.
The other option is to put in computer another disk and install small Linux installation with X and some old fashioned window manager that will be rescue and boot system. Disadvantage is that you will have to update both when kernel update is due.
Third is to backup /home and start from scratch. Create partitions before you start installation, for instance from Live CD, and then run installation.
I did manage to boot from the installation DVD and get rsync working. I then created anothe OSE11.3 VM and rsync'ed /home and /etc to the new VM. I kept the old one around to see if I can learn by trying to fix it. Unfortunately, time has not permitted. On the new VM, I opted for non-LVM partitions for all of the OS stuff and did away with the separate /boot partition altogether which seems to be the recommendation of more experienced SuSE folks (and even Red Hat too). I have a minimal OSE11.3 VM at work which I installed taking the defaults which created a separate 68MB /boot. I realize the separate /boot is probably required because I chose the LVM route for root (/) and the other OS partitions. I did not try to resize it at that time because it is really not used for much. I cannot even put it on the network to update it without violating our "security" policies but don't get me started on that one!
In any case it will be interesting to know what exactly what you did with current installation. I didn't have problems with installer, but I don't use separate boot, and LVM. If it did not allow you to make partition bigger then 68M then you should file a bug report.
When I recall that my first 2 hard disks were 80MB :)
My first hard drive was on a Tandy 1000 running DOS 3. I bought a third party controller and 20MB hard drive wondering how I would ever use that much space! My latest ESXi box has four 750GB drives in a RAID5 with hot spare giving about 1.4TB usable. How will I ever use that much space ... <G>! Thank you, Lucky Leavell -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I'd remove everything except grub and at least one each of working kernel & initrd from the /boot partition by umounting from /boot and mounting it (permanently) on /mnt/boot. This means you still boot from the same partition as before, but just do not mount it on /boot during normal operation, which means you must maintain it (realboot) manually. 68M is enough for a modest number of kernels and initrds. It wasn't too many years ago that a mere 75M was the RedHat recommended minimum size for /boot. Why the installer refused to allow a larger /boot in the first place ought to be investigated and prevented from biting again. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010-09-19 02:07, Felix Miata wrote:
Why the installer refused to allow a larger /boot in the first place ought to be investigated and prevented from biting again.
That's weird, mine has 200 MB. And I think it complained it was too small. -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))
participants (5)
-
Carlos E. R. -
Cristian Rodríguez -
Felix Miata -
Lucky Leavell -
Rajko M.