Prev: how to stop RHEL (or OEL) from trying to mount other disks notin fstab
Next: Now, my Debian thinks I have SCSI for my old IDE/ATA drives after installing Kernel 2.6.32-4?
From: Pascal Hambourg on 25 Apr 2010 16:55 David W. Hodgins a �crit : > On Sun, 25 Apr 2010 15:00:57 -0400, Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: > >>> If you have a partition called /dev/hda16, using the new kernel will >>> cause a lot of problems. >> >> What kind of problems except that the partition won't be usable ? > > If you attempt to make any changes to the existing partitions, you > risk losing the unaccessible partitions. Messing up the chain of > extended partition tables is really undesirable. Really ? AFAIK, partitioning tools do not suffer from the kernel limitation, as they access directly the partition table from the disk.
From: David W. Hodgins on 26 Apr 2010 17:42 On Sun, 25 Apr 2010 16:55:14 -0400, Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: > Really ? AFAIK, partitioning tools do not suffer from the kernel > limitation, as they access directly the partition table from the disk. I have to agree it probably won't cause any problems, with most partitioning tools. Some distributions, such as Mandriva, do include gui partitioning tools (diskdrake), that do use the info from the kernel, to decide what parameters to pass to the actual partitioning tools. I have not tested using such a tool, with a drive with more than 15 partitions, to see what will happen. Risking messing up the chain of extended partition tables, is something I'm very cautious with. I have had the fun of rebuilding partition tables and chains, when a user managed to mess things up. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.)
From: David W. Hodgins on 26 Apr 2010 17:22
On Mon, 26 Apr 2010 13:09:53 -0400, Robert Wolfe <robert(a)news.robertwolfe.org> wrote: > Myself, I prefer using the -h option after df and dh. Makes things a > little bit easier to read :) In my case, I was once hit with the problem of a full root filesystem, after which I split /boot, /home, /opt, /usr, /tmp, and /var into separate filesystems. Since I found that memtest will not boot from a separate partition, I stopped splitting that out of /. At the point where I switched to a kernel that used the libata module for ide drives, I had two versions of Mandriva linux installeld, as well as four very old vfat partitions for w98, and one ntfs for xp. Although I'd recently removed slackware and gentoo, I still had a hda16 partition. It was easy to move things around to get rid of it, but it would have been more difficult if I'd chosen to keep the older slackware and gentoo installations. At present, I use a shared swap filesystem with all linux installs, and three separate partitions for each linux install. One for /, one for /var/log, and one lvm partition for the rest. I keep / and /var/log on real partitions, as at the time I set it up that way, the knoppix cd I was normally using as my rescue cd, did not support lvm. For each linux install (I currently have three), df shows ... $ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda14 1004M 514M 440M 54% / /dev/mapper/91-home 1008M 777M 181M 82% /home /dev/mapper/91-opt 1008M 413M 545M 44% /opt /dev/mapper/91-tmp 5.5G 158M 5.0G 3% /tmp /dev/mapper/91-usr 16G 12G 3.7G 76% /usr /dev/mapper/91-var 7.9G 1.1G 6.5G 14% /var /dev/sda15 494M 77M 393M 17% /var/log /dev/mapper/91-mnt 3.9M 76K 3.6M 3% /var/mnt I symlink /mnt and /media to /var/mnt, so that if I try to copy a large file, to an unmounted filesystem, it fills that filesystem very quickly, instead of filling the / filesystem. (That was how I ended up with a full / filesystem, that one time). Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.) |