Re: Resizing partitions on a headless server
csanyi...@gmail.com a écrit : I want to create one LV for /usr and one LV for /var. But I can't create a LV with: # lvcreate --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB /dev/bubba/usr: not found: device not cleared Aborting. Failed to wipe start of new LV. semid 1114120: semop failed for cookie 0xd4d6ff6: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223178742 (0xd4d6ff6) to initialize waiting for incoming notifications. I don't understand why can't create a new LV with this command abowe? Never had this error before. From a quick search, it may be related to hotplug/udev event processing. In which environment are you running this command ? What happens if you add the option --noudevsync ? And don't understand why is successful following command? # lvcreate -vvv --size 10.10G -n usr bubba -v just increases the verbosity, so it should not have any effect on success or failure. I search on Internet and found another solution: # lvcreate -Zn --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB WARNING: bubba/usr not zeroed Logical volume usr created semid 1146888: semop failed for cookie 0xd4d9b50: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223189840 (0xd4d9b50) to initialize waiting for incoming notifications. That's not a solution, just a workaround to avoid the wiping error. Can I use now this newly created LV to make on it an ext4 filesystem despite the fact that it is not zeroed? Yes, if it is created correctly and active. Check with lvs, lvdisplay. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5586cc60.5090...@plouf.fr.eu.org
Re: Resizing partitions on a headless server
A small contribution, perhaps unnecessary. To change the size of a lvs with lvreduce or lvextend is important to use the resize2fs and e2fsck command. Good luck in solving the problem On Sun, Jun 21, 2015 at 11:38 AM, Pascal Hambourg pas...@plouf.fr.eu.org wrote: csanyi...@gmail.com a écrit : I want to create one LV for /usr and one LV for /var. But I can't create a LV with: # lvcreate --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB /dev/bubba/usr: not found: device not cleared Aborting. Failed to wipe start of new LV. semid 1114120: semop failed for cookie 0xd4d6ff6: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223178742 (0xd4d6ff6) to initialize waiting for incoming notifications. I don't understand why can't create a new LV with this command abowe? Never had this error before. From a quick search, it may be related to hotplug/udev event processing. In which environment are you running this command ? What happens if you add the option --noudevsync ? And don't understand why is successful following command? # lvcreate -vvv --size 10.10G -n usr bubba -v just increases the verbosity, so it should not have any effect on success or failure. I search on Internet and found another solution: # lvcreate -Zn --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB WARNING: bubba/usr not zeroed Logical volume usr created semid 1146888: semop failed for cookie 0xd4d9b50: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223189840 (0xd4d9b50) to initialize waiting for incoming notifications. That's not a solution, just a workaround to avoid the wiping error. Can I use now this newly created LV to make on it an ext4 filesystem despite the fact that it is not zeroed? Yes, if it is created correctly and active. Check with lvs, lvdisplay. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5586cc60.5090...@plouf.fr.eu.org -- Gustavo Soares de Lima
Re: Resizing partitions on a headless server
Pascal Hambourg pas...@plouf.fr.eu.org writes: csanyi...@gmail.com a écrit : I want to create one LV for /usr and one LV for /var. But I can't create a LV with: # lvcreate --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB /dev/bubba/usr: not found: device not cleared Aborting. Failed to wipe start of new LV. semid 1114120: semop failed for cookie 0xd4d6ff6: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223178742 (0xd4d6ff6) to initialize waiting for incoming notifications. I don't understand why can't create a new LV with this command abowe? Never had this error before. From a quick search, it may be related to hotplug/udev event processing. In which environment are you running this command ? What happens if you add the option --noudevsync ? # lvcreate --noudevsync --size 10.10G -n var bubba Rounding up size to full physical extent 10.10 GiB /dev/bubba/var: not found: device not cleared Aborting. Failed to wipe start of new LV. This is a Debian GNU/Linux Jessie on power pc headless box. Furthermore, I don't think so so udev is properly setup on this system. I red in /etc/udev/udev.conf the followings: [quote] # udevd is started in the initramfs, so when this file is modified the # initramfs should be rebuilt. [/quote] In this file I remove the # from the beginning of line: udev_log=info but don't know how to rebuild initramfs? In /boot I have these files: 8313E21.dtb System.map-3.2.62-1 bubba.dtb config-3.2.62-1 uImage This is a power pc box on which booting process is started with u-boot. Can I describe this environment better? And don't understand why is successful following command? # lvcreate -vvv --size 10.10G -n usr bubba -v just increases the verbosity, so it should not have any effect on success or failure. I search on Internet and found another solution: # lvcreate -Zn --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB WARNING: bubba/usr not zeroed Logical volume usr created semid 1146888: semop failed for cookie 0xd4d9b50: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223189840 (0xd4d9b50) to initialize waiting for incoming notifications. That's not a solution, just a workaround to avoid the wiping error. Can I use now this newly created LV to make on it an ext4 filesystem despite the fact that it is not zeroed? Yes, if it is created correctly and active. Check with lvs, lvdisplay. # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log \ Cpy%Sync Convert storage bubba -wi-a- 20.10g usr bubba -wi-a- 10.10g # lvdisplay --- Logical volume --- LV Path/dev/bubba/usr LV Nameusr VG Namebubba LV UUIDEe83A0-H6J3-w4Xi-bt1f-3zGN-jVm4-DOUKxq LV Write Accessread/write LV Creation host, time b2, 2015-06-19 07:26:48 +0200 LV Status available # open 0 LV Size10.10 GiB Current LE 2586 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/871th5t3ah@gmail.com
Re: Resizing partitions on a headless server
Pascal Hambourg pas...@plouf.fr.eu.org writes: csanyi...@gmail.com a écrit : Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage Glad you were lucky. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 As one can see, my /dev/root partition is almost full. I want to increase /dev/root partition to be maximum available size and decrease /home partition to only 20 GiB. So can be the /var directory large enough to encompass the web and other contents. What are your advises, what do I do to reach my goal? Do not resize partitions. This is difficult and risky. Use LVM. Reduce the filesystem in the LV and the LV to a adequate size (without mistake this time). I did this step successfully: root@b2:~# pvdisplay --- Physical volume --- PV Name /dev/sda2 VG Name bubba PV Size 455.43 GiB / not usable 3.65 MiB Allocatable yes PE Size 4.00 MiB Total PE 116588 Free PE 111442 Allocated PE 5146 PV UUID SMvR2K-6Z3c-xCgd-jSR2-kb1A-15a2-3RiS6V root@b2:~# lvdisplay --- Logical volume --- LV Path/dev/bubba/storage LV Namestorage VG Namebubba LV UUID91yHxQ-RmOW-OeDv-jaIv-1z1B-KBSk-yCsDC6 LV Write Accessread/write LV Creation host, time , LV Status available # open 1 LV Size20.10 GiB Current LE 5146 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 Create a new LV of adequate size. DON'T take all the available space in the VG. Leave some space for future needs. Increasing a LV and its filesystem is easy and can be done online while it's mounted. Reducing is risky, as you experienced. I want to create one LV for /usr and one LV for /var. But I can't create a LV with: # lvcreate --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB /dev/bubba/usr: not found: device not cleared Aborting. Failed to wipe start of new LV. semid 1114120: semop failed for cookie 0xd4d6ff6: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223178742 (0xd4d6ff6) to initialize waiting for incoming notifications. I don't understand why can't create a new LV with this command abowe? And don't understand why is successful following command? # lvcreate -vvv --size 10.10G -n usr bubba I search on Internet and found another solution: # lvcreate -Zn --size 10.10G -n usr bubba Rounding up size to full physical extent 10.10 GiB WARNING: bubba/usr not zeroed Logical volume usr created semid 1146888: semop failed for cookie 0xd4d9b50: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223189840 (0xd4d9b50) to initialize waiting for incoming notifications. Can I use now this newly created LV to make on it an ext4 filesystem despite the fact that it is not zeroed? -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87wpz0461s@gmail.com
Re: Resizing partitions on a headless server
On Mon, Jun 15, 2015 at 08:25:09AM +0200, csanyi...@gmail.com wrote: I bought the headless powerpc server here: http://www.excitostore.com/ If you mean the Excito B3, it would appear to be ARM, not PowerPC. That's good for you because ARM is still a supported architecture in Debian, and PowerPC is not. I get the hardware preinstalled with Debian Sarge. The developers knows why did the partition so as is. Really? Sarge is ancient. The website says it comes with Squeeze... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150615092931.gc21...@chew.redmars.org
Re: Resizing partitions on a headless server
Jonathan Dowland j...@debian.org writes: On Mon, Jun 15, 2015 at 08:25:09AM +0200, csanyi...@gmail.com wrote: I bought the headless powerpc server here: http://www.excitostore.com/ If you mean the Excito B3, it would appear to be ARM, not PowerPC. That's good for you because ARM is still a supported architecture in Debian, and PowerPC is not. No B3 but B2 and B2 is power pc. I get the hardware preinstalled with Debian Sarge. The developers knows why did the partition so as is. Really? Sarge is ancient. The website says it comes with Squeeze... Well, I can't remember which Debian distribution came with Bubba Two. It came maybe with etch or lenny? Bubba 3 is a different story. -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87r3pdrney@gmail.com
Re: Resizing partitions on a headless server
Jonathan Dowland j...@debian.org writes: On Mon, Jun 15, 2015 at 08:25:09AM +0200, csanyi...@gmail.com wrote: I bought the headless powerpc server here: http://www.excitostore.com/ If you mean the Excito B3, it would appear to be ARM, not PowerPC. That's good for you because ARM is still a supported architecture in Debian, and PowerPC is not. Wrong, PowerPC is supported architecture: https://www.debian.org/releases/stable/ -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87lhflrn8s@gmail.com
Re: Resizing partitions on a headless server
Pascal Hambourg pas...@plouf.fr.eu.org writes: csanyi...@gmail.com a écrit : Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage Glad you were lucky. Now, I can to use parted to resize my partitions. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 # fdisk -l Device Boot Start End Sectors Size Id Type /dev/sda1 63 19551104 19551042 9.3G 83 Linux /dev/sda219551105 974647484 955096380 455.4G 8e Linux LVM /dev/sda3 974647485 976768064 2120580 1G 82 Linux swap / Solaris # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert storage bubba -wi-ao 455.40g # pvs PV VGFmt Attr PSize PFree /dev/sda2 bubba lvm2 a-- 455.42g 20.00m I'm curious : what's the use of LVM if you have only one LV taking all the space in the VG, and plain partitions outside the VG ? I bought the headless powerpc server here: http://www.excitostore.com/ I get the hardware preinstalled with Debian Sarge. The developers knows why did the partition so as is. -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87wpz5o5ru@gmail.com
Re: Resizing partitions on a headless server
Pascal Hambourg pas...@plouf.fr.eu.org writes: csanyi...@gmail.com a écrit : Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage Glad you were lucky. Now, I can to use parted to resize my partitions. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 # fdisk -l Device Boot Start End Sectors Size Id Type /dev/sda1 63 19551104 19551042 9.3G 83 Linux /dev/sda219551105 974647484 955096380 455.4G 8e Linux LVM /dev/sda3 974647485 976768064 2120580 1G 82 Linux swap / Solaris # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert storage bubba -wi-ao 455.40g # pvs PV VGFmt Attr PSize PFree /dev/sda2 bubba lvm2 a-- 455.42g 20.00m I'm curious : what's the use of LVM if you have only one LV taking all the space in the VG, and plain partitions outside the VG ? I bought the headless powerpc server here: http://www.excitostore.com/ I get the hardware preinstalled with Debian Sarge. The developers knows why did the partition so as is. -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87egldo5dm@gmail.com
Re: Resizing partitions on a headless server
On 14/06/15 12:40 AM, csanyi...@gmail.com wrote: Gary Dale garyd...@torfree.net writes: On 13/06/15 03:19 PM, csanyi...@gmail.com wrote: Hello, on my headless Debian GNU/Linux Jessie server I want to resize partitions. So far I did followings: root@b2:~# df -T FilesystemType 1K-blocksUsed Available Use% Mounted on /dev/root ext3 9621848 8293064840008 91% / devtmpfs devtmpfs127800 0127800 0% /dev tmpfs tmpfs 127880 4127876 1% /dev/shm tmpfs tmpfs 127880 17992109888 15% /run tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 127880 0127880 0% /sys/fs/cgroup /dev/mapper/bubba-storage ext3 470050224 8512368 437660636 2% /home tmpfs tmpfs25576 0 25576 0% /run/user/1001 tmpfs tmpfs25576 0 25576 0% /run/user/0 root@b2:~# umount /dev/mapper/bubba-storage root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G resize2fs 1.42.12 (29-Aug-2014) Please run 'e2fsck -f /dev/mapper/bubba-storage' first. root@b2:~# e2fsck -f /dev/mapper/bubba-storage e2fsck 1.42.12 (29-Aug-2014) 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 Bubba_home: 114439/59703296 files (0.4% non-contiguous), \ 4001648/119386112 blocks At this step I think I forgot to run again: root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G root@b2:~# lvresize --size 2.1G /dev/mapper/bubba-storage Rounding size to boundary between physical extents: 2.10 GiB WARNING: Reducing active logical volume to 2.10 GiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce storage? [y/n]: y Size of logical volume bubba/storage changed from 455.42 GiB (116588 extents) to 2.10 GiB (538 extents). Logical volume storage successfully resized Furthermore, I was wrong when I determined the --size to 2.1G in the command abowe, because I wanted to write 20.1G instead. root@b2:~# resize2fs -p /dev/mapper/bubba-storage resize2fs 1.42.12 (29-Aug-2014) resize2fs: New size smaller than minimum (2153070) root@b2:~# mount /dev/mapper/bubba-storage After these steps I rebooted the server but can't login on it with ssh but only with serial cable. Now, when I login on the serial console as non root user, I get messages: b2 login: csanyipal Password: EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 Last login: Sat Jun 13 14:06:27 CEST 2015 from 192.168.10.90 on pts/0 Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 No directory, logging in with HOEXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 ME=/ Now what can I do to correct the partitions? Boot from something like system rescue CD and try to fix the damage. With any luck resize2fs didn't do anything. Hopefully you can put the partitions back the way they were. My headless powerpc box can't boot from CD because it hasn't CD device. It only has USB drive. Furthermore, it can't boot with an usual system rescue image installed on USB stick, because it uses uImage. I tried systemrescuecd ( http://www.sysresccd.org ), gparted live to boot with, but without success. I think I have the possibility to use serial console only. There I can run parted but don't know how to fix with it the problem I made. Otherwise, there is always testdisk or your backups. I just installed testdisk and try followings: Select a media: Disk /dev/sda - 500 GB / 465 GiB - WDC WD5000AACS-00G8B1 Disk /dev/mapper/bubba-storage - 2256 MB / 2152 MiB - WDC \ WD5000AACS-00G8B1 Disk /dev/dm-0 - 2256 MB / 2152 MiB - WDC WD5000AACS-00G8B1 [Proceed ] Please select the partition table type, press Enter when done. [Humax ] Humax partition table Hint: Humax partition table type has been detected. Disk /dev/sda - 500 GB / 465 GiB - WDC WD5000AACS-00G8B1 CHS 60801 255 63 - sector size=512 [ Analyse ] Disk /dev/sda - 500 GB / 465 GiB - CHS 60801 255 63 Current partition structure:
Re: Resizing partitions on a headless server
csanyi...@gmail.com writes: Gary Dale garyd...@torfree.net writes: On 13/06/15 03:19 PM, csanyi...@gmail.com wrote: [snipped] My headless powerpc box can't boot from CD because it hasn't CD device. It only has USB drive. Furthermore, it can't boot with an usual system rescue image installed on USB stick, because it uses uImage. I tried systemrescuecd ( http://www.sysresccd.org ), gparted live to boot with, but without success. I think I have the possibility to use serial console only. There I can run parted but don't know how to fix with it the problem I made. Otherwise, there is always testdisk or your backups. I just installed testdisk and try followings: [snipped] Segmentation fault So, I can't use testdisk here. Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage # resize2fs -p /dev/mapper/bubba-storage # reboot So now I get back my /home partition and can ssh into my server. Now, I can to use parted to resize my partitions. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 # fdisk -l Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Device Boot Start End Sectors Size Id Type /dev/sda1 63 19551104 19551042 9.3G 83 Linux /dev/sda219551105 974647484 955096380 455.4G 8e Linux LVM /dev/sda3 974647485 976768064 2120580 1G 82 Linux swap / Solaris # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert storage bubba -wi-ao 455.40g # pvs PV VGFmt Attr PSize PFree /dev/sda2 bubba lvm2 a-- 455.42g 20.00m As one can see, my /dev/root partition is almost full. I want to increase /dev/root partition to be maximum available size and decrease /home partition to only 20 GiB. So can be the /var directory large enough to encompass the web and other contents. What are your advises, what do I do to reach my goal? -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87pp4ylblc@gmail.com
Re: Resizing partitions on a headless server
On 14/06/15 08:26 AM, csanyi...@gmail.com wrote: csanyi...@gmail.com writes: Gary Dale garyd...@torfree.net writes: On 13/06/15 03:19 PM, csanyi...@gmail.com wrote: [snipped] My headless powerpc box can't boot from CD because it hasn't CD device. It only has USB drive. Furthermore, it can't boot with an usual system rescue image installed on USB stick, because it uses uImage. I tried systemrescuecd ( http://www.sysresccd.org ), gparted live to boot with, but without success. I think I have the possibility to use serial console only. There I can run parted but don't know how to fix with it the problem I made. Otherwise, there is always testdisk or your backups. I just installed testdisk and try followings: [snipped] Segmentation fault So, I can't use testdisk here. Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage # resize2fs -p /dev/mapper/bubba-storage # reboot So now I get back my /home partition and can ssh into my server. Now, I can to use parted to resize my partitions. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 # fdisk -l Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Device Boot Start End Sectors Size Id Type /dev/sda1 63 19551104 19551042 9.3G 83 Linux /dev/sda219551105 974647484 955096380 455.4G 8e Linux LVM /dev/sda3 974647485 976768064 2120580 1G 82 Linux swap / Solaris # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert storage bubba -wi-ao 455.40g # pvs PV VGFmt Attr PSize PFree /dev/sda2 bubba lvm2 a-- 455.42g 20.00m As one can see, my /dev/root partition is almost full. I want to increase /dev/root partition to be maximum available size and decrease /home partition to only 20 GiB. So can be the /var directory large enough to encompass the web and other contents. What are your advises, what do I do to reach my goal? My advice is to leave well enough alone until such time as you are fully comfortable using the tools. Then proceed modifying one partition at a time and verifying that it has worked before trying to do anything else. You've just wasted a lot of time trying to do too much at once. This is your data that you are playing with. Some extra umount/adjust/mount cycles are a small price to pay for minimizing the risk to your files. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d816f.4030...@torfree.net
Re: Resizing partitions on a headless server
csanyi...@gmail.com a écrit : Hello, on my headless Debian GNU/Linux Jessie server I want to resize partitions. Why ? The use of LVM should avoid the need to resize partitions (PVs). root@b2:~# e2fsck -f /dev/mapper/bubba-storage e2fsck 1.42.12 (29-Aug-2014) 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 Bubba_home: 114439/59703296 files (0.4% non-contiguous), \ 4001648/119386112 blocks At this step I think I forgot to run again: root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G root@b2:~# lvresize --size 2.1G /dev/mapper/bubba-storage Rounding size to boundary between physical extents: 2.10 GiB WARNING: Reducing active logical volume to 2.10 GiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce storage? [y/n]: y Size of logical volume bubba/storage changed from 455.42 GiB (116588 extents) to 2.10 GiB (538 extents). Logical volume storage successfully resized Furthermore, I was wrong when I determined the --size to 2.1G in the command abowe, because I wanted to write 20.1G instead. The bad news is that you probably screwed the filesystem. LVM provides flexibility over plain partitions, but at the cost of complexity and is less tolerant to such a mistake. With a plain partition, all you would have to do to fix the mistake is to extend the reduced partition (not the filesystem) to its original size. However, with LVM, if you extend a reduced LV to its original size, nothing guarantees that it will use the same physical blocks as before. You can try, but it may not restore the filesystem's integrity. Run fsck to check the damage. Edit : check in /etc/lvm/backup for a metadata backup of the previous situation of the VG bubba. Using it to restore the LV is beyond my knowledge, but if your data is important and you don't have a backup (sounds like an oxymoron), my advice is don't touch anything until you find how to restore the LV. Otherwise, just extend the LV and recreate the filesystem on it. Now what can I do to correct the partitions? There is no partition to correct. The problem is in the LV bubba/storage and its filesystem. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d7dbd.7020...@plouf.fr.eu.org
Re: Resizing partitions on a headless server
csanyi...@gmail.com a écrit : Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage Glad you were lucky. Now, I can to use parted to resize my partitions. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 # fdisk -l Device Boot Start End Sectors Size Id Type /dev/sda1 63 19551104 19551042 9.3G 83 Linux /dev/sda219551105 974647484 955096380 455.4G 8e Linux LVM /dev/sda3 974647485 976768064 2120580 1G 82 Linux swap / Solaris # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert storage bubba -wi-ao 455.40g # pvs PV VGFmt Attr PSize PFree /dev/sda2 bubba lvm2 a-- 455.42g 20.00m I'm curious : what's the use of LVM if you have only one LV taking all the space in the VG, and plain partitions outside the VG ? As one can see, my /dev/root partition is almost full. I want to increase /dev/root partition to be maximum available size and decrease /home partition to only 20 GiB. So can be the /var directory large enough to encompass the web and other contents. What are your advises, what do I do to reach my goal? Do not resize partitions. This is difficult and risky. Use LVM. Reduce the filesystem in the LV and the LV to a adequate size (without mistake this time). Create a new LV of adequate size. DON'T take all the available space in the VG. Leave some space for future needs. Increasing a LV and its filesystem is easy and can be done online while it's mounted. Reducing is risky, as you experienced. Move the data in /var from the root filesystem to the new LV and mount it on /var. Update /etc/fstab accordingly. Or : Create a var directory in /home Move the data in /var to /home/var Bind-mount /home/var on /var and update /etc/fstab. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d8290.6070...@plouf.fr.eu.org
Re: Resizing partitions on a headless server
On 14/06/15 09:12 AM, Pascal Hambourg wrote: csanyi...@gmail.com a écrit : Hello, on my headless Debian GNU/Linux Jessie server I want to resize partitions. Why ? The use of LVM should avoid the need to resize partitions (PVs). root@b2:~# e2fsck -f /dev/mapper/bubba-storage e2fsck 1.42.12 (29-Aug-2014) 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 Bubba_home: 114439/59703296 files (0.4% non-contiguous), \ 4001648/119386112 blocks At this step I think I forgot to run again: root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G root@b2:~# lvresize --size 2.1G /dev/mapper/bubba-storage Rounding size to boundary between physical extents: 2.10 GiB WARNING: Reducing active logical volume to 2.10 GiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce storage? [y/n]: y Size of logical volume bubba/storage changed from 455.42 GiB (116588 extents) to 2.10 GiB (538 extents). Logical volume storage successfully resized Furthermore, I was wrong when I determined the --size to 2.1G in the command abowe, because I wanted to write 20.1G instead. The bad news is that you probably screwed the filesystem. LVM provides flexibility over plain partitions, but at the cost of complexity and is less tolerant to such a mistake. With a plain partition, all you would have to do to fix the mistake is to extend the reduced partition (not the filesystem) to its original size. However, with LVM, if you extend a reduced LV to its original size, nothing guarantees that it will use the same physical blocks as before. You can try, but it may not restore the filesystem's integrity. Run fsck to check the damage. Edit : check in /etc/lvm/backup for a metadata backup of the previous situation of the VG bubba. Using it to restore the LV is beyond my knowledge, but if your data is important and you don't have a backup (sounds like an oxymoron), my advice is don't touch anything until you find how to restore the LV. Otherwise, just extend the LV and recreate the filesystem on it. Now what can I do to correct the partitions? There is no partition to correct. The problem is in the LV bubba/storage and its filesystem. If you read the original post, it looks like the e2rsize failed. Therefor the only problem is the partition table is wrong. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d8a79.4060...@torfree.net
Re: Resizing partitions on a headless server
Pascal Hambourg pas...@plouf.fr.eu.org writes: csanyi...@gmail.com a écrit : Finally, I solved the problem by doing the followings: # lvresize --size 455.5G /dev/mapper/bubba-storage # e2fsck -f /dev/mapper/bubba-storage Glad you were lucky. Now, I can to use parted to resize my partitions. What is my goal? Filesystem Size Used Avail Use% Mounted on /dev/root 9.2G 8.0G 815M 91% / devtmpfs 125M 0 125M 0% /dev tmpfs 125M 4.0K 125M 1% /dev/shm tmpfs 125M 5.6M 120M 5% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 125M 0 125M 0% /sys/fs/cgroup /dev/mapper/bubba-storage 449G 8.2G 418G 2% /home tmpfs 25M 0 25M 0% /run/user/1001 # fdisk -l Device Boot Start End Sectors Size Id Type /dev/sda1 63 19551104 19551042 9.3G 83 Linux /dev/sda219551105 974647484 955096380 455.4G 8e Linux LVM /dev/sda3 974647485 976768064 2120580 1G 82 Linux swap / Solaris # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert storage bubba -wi-ao 455.40g # pvs PV VGFmt Attr PSize PFree /dev/sda2 bubba lvm2 a-- 455.42g 20.00m I'm curious : what's the use of LVM if you have only one LV taking all the space in the VG, and plain partitions outside the VG ? I bought thie headless powerpc server here: http://www.excitostore.com/ I get the hardware preinstalled with Debian Sarge. The developer knows why did the partition so. -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87bngikudq@gmail.com
Re: Resizing partitions on a headless server
csanyi...@gmail.com a écrit : Gary Dale garyd...@torfree.net writes: On 14/06/15 09:12 AM, Pascal Hambourg wrote: There is no partition to correct. The problem is in the LV bubba/storage and its filesystem. If you read the original post, it looks like the e2rsize failed. Therefor the only problem is the partition table is wrong. No command mentionned by the OP ever modified the partition table. Modifying LVM logical volumes and filesystems does not modify the partition table. They have their own metadata. I think now is everything fixed, the partition table also. Am I right? Hopefully yes. You were lucky this time. The partition table was never modified. How can be sure? After reboot I can login as non root user, I can find my ( not so valuable ) data on /home, .. Well, if fsck -f did not complain and your files are back, you can be pretty confident. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557dbc3f@plouf.fr.eu.org
Re: Resizing partitions on a headless server
Gary Dale garyd...@torfree.net writes: On 14/06/15 09:12 AM, Pascal Hambourg wrote: csanyi...@gmail.com a écrit : Hello, on my headless Debian GNU/Linux Jessie server I want to resize partitions. Why ? The use of LVM should avoid the need to resize partitions (PVs). root@b2:~# e2fsck -f /dev/mapper/bubba-storage e2fsck 1.42.12 (29-Aug-2014) 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 Bubba_home: 114439/59703296 files (0.4% non-contiguous), \ 4001648/119386112 blocks At this step I think I forgot to run again: root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G root@b2:~# lvresize --size 2.1G /dev/mapper/bubba-storage Rounding size to boundary between physical extents: 2.10 GiB WARNING: Reducing active logical volume to 2.10 GiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce storage? [y/n]: y Size of logical volume bubba/storage changed from 455.42 GiB (116588 extents) to 2.10 GiB (538 extents). Logical volume storage successfully resized Furthermore, I was wrong when I determined the --size to 2.1G in the command abowe, because I wanted to write 20.1G instead. The bad news is that you probably screwed the filesystem. LVM provides flexibility over plain partitions, but at the cost of complexity and is less tolerant to such a mistake. With a plain partition, all you would have to do to fix the mistake is to extend the reduced partition (not the filesystem) to its original size. However, with LVM, if you extend a reduced LV to its original size, nothing guarantees that it will use the same physical blocks as before. You can try, but it may not restore the filesystem's integrity. Run fsck to check the damage. Edit : check in /etc/lvm/backup for a metadata backup of the previous situation of the VG bubba. Using it to restore the LV is beyond my knowledge, but if your data is important and you don't have a backup (sounds like an oxymoron), my advice is don't touch anything until you find how to restore the LV. Otherwise, just extend the LV and recreate the filesystem on it. Now what can I do to correct the partitions? There is no partition to correct. The problem is in the LV bubba/storage and its filesystem. If you read the original post, it looks like the e2rsize failed. Therefor the only problem is the partition table is wrong. I think now is everything fixed, the partition table also. Am I right? How can be sure? After reboot I can login as non root user, I can find my ( not so valuable ) data on /home, .. -- Regards from Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87k2v6l4ne@gmail.com
Re: Resizing partitions on a headless server
On 13/06/15 03:19 PM, csanyi...@gmail.com wrote: Hello, on my headless Debian GNU/Linux Jessie server I want to resize partitions. So far I did followings: root@b2:~# df -T FilesystemType 1K-blocksUsed Available Use% Mounted on /dev/root ext3 9621848 8293064840008 91% / devtmpfs devtmpfs127800 0127800 0% /dev tmpfs tmpfs 127880 4127876 1% /dev/shm tmpfs tmpfs 127880 17992109888 15% /run tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 127880 0127880 0% /sys/fs/cgroup /dev/mapper/bubba-storage ext3 470050224 8512368 437660636 2% /home tmpfs tmpfs25576 0 25576 0% /run/user/1001 tmpfs tmpfs25576 0 25576 0% /run/user/0 root@b2:~# umount /dev/mapper/bubba-storage root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G resize2fs 1.42.12 (29-Aug-2014) Please run 'e2fsck -f /dev/mapper/bubba-storage' first. root@b2:~# e2fsck -f /dev/mapper/bubba-storage e2fsck 1.42.12 (29-Aug-2014) 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 Bubba_home: 114439/59703296 files (0.4% non-contiguous), \ 4001648/119386112 blocks At this step I think I forgot to run again: root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G root@b2:~# lvresize --size 2.1G /dev/mapper/bubba-storage Rounding size to boundary between physical extents: 2.10 GiB WARNING: Reducing active logical volume to 2.10 GiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce storage? [y/n]: y Size of logical volume bubba/storage changed from 455.42 GiB (116588 extents) to 2.10 GiB (538 extents). Logical volume storage successfully resized Furthermore, I was wrong when I determined the --size to 2.1G in the command abowe, because I wanted to write 20.1G instead. root@b2:~# resize2fs -p /dev/mapper/bubba-storage resize2fs 1.42.12 (29-Aug-2014) resize2fs: New size smaller than minimum (2153070) root@b2:~# mount /dev/mapper/bubba-storage After these steps I rebooted the server but can't login on it with ssh but only with serial cable. Now, when I login on the serial console as non root user, I get messages: b2 login: csanyipal Password: EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 Last login: Sat Jun 13 14:06:27 CEST 2015 from 192.168.10.90 on pts/0 Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 No directory, logging in with HOEXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 ME=/ Now what can I do to correct the partitions? Boot from something like system rescue CD and try to fix the damage. With any luck resize2fs didn't do anything. Hopefully you can put the partitions back the way they were. Otherwise, there is always testdisk or your backups. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557cf6de.8030...@torfree.net
Re: Resizing partitions on a headless server
Gary Dale garyd...@torfree.net writes: On 13/06/15 03:19 PM, csanyi...@gmail.com wrote: Hello, on my headless Debian GNU/Linux Jessie server I want to resize partitions. So far I did followings: root@b2:~# df -T FilesystemType 1K-blocksUsed Available Use% Mounted on /dev/root ext3 9621848 8293064840008 91% / devtmpfs devtmpfs127800 0127800 0% /dev tmpfs tmpfs 127880 4127876 1% /dev/shm tmpfs tmpfs 127880 17992109888 15% /run tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 127880 0127880 0% /sys/fs/cgroup /dev/mapper/bubba-storage ext3 470050224 8512368 437660636 2% /home tmpfs tmpfs25576 0 25576 0% /run/user/1001 tmpfs tmpfs25576 0 25576 0% /run/user/0 root@b2:~# umount /dev/mapper/bubba-storage root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G resize2fs 1.42.12 (29-Aug-2014) Please run 'e2fsck -f /dev/mapper/bubba-storage' first. root@b2:~# e2fsck -f /dev/mapper/bubba-storage e2fsck 1.42.12 (29-Aug-2014) 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 Bubba_home: 114439/59703296 files (0.4% non-contiguous), \ 4001648/119386112 blocks At this step I think I forgot to run again: root@b2:~# resize2fs -p /dev/mapper/bubba-storage 20G root@b2:~# lvresize --size 2.1G /dev/mapper/bubba-storage Rounding size to boundary between physical extents: 2.10 GiB WARNING: Reducing active logical volume to 2.10 GiB THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce storage? [y/n]: y Size of logical volume bubba/storage changed from 455.42 GiB (116588 extents) to 2.10 GiB (538 extents). Logical volume storage successfully resized Furthermore, I was wrong when I determined the --size to 2.1G in the command abowe, because I wanted to write 20.1G instead. root@b2:~# resize2fs -p /dev/mapper/bubba-storage resize2fs 1.42.12 (29-Aug-2014) resize2fs: New size smaller than minimum (2153070) root@b2:~# mount /dev/mapper/bubba-storage After these steps I rebooted the server but can't login on it with ssh but only with serial cable. Now, when I login on the serial console as non root user, I get messages: b2 login: csanyipal Password: EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 Last login: Sat Jun 13 14:06:27 CEST 2015 from 192.168.10.90 on pts/0 Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 No directory, logging in with HOEXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=30752769, block=61505538 ME=/ Now what can I do to correct the partitions? Boot from something like system rescue CD and try to fix the damage. With any luck resize2fs didn't do anything. Hopefully you can put the partitions back the way they were. My headless powerpc box can't boot from CD because it hasn't CD device. It only has USB drive. Furthermore, it can't boot with an usual system rescue image installed on USB stick, because it uses uImage. I tried systemrescuecd ( http://www.sysresccd.org ), gparted live to boot with, but without success. I think I have the possibility to use serial console only. There I can run parted but don't know how to fix with it the problem I made. Otherwise, there is always testdisk or your backups. I just installed testdisk and try followings: Select a media: Disk /dev/sda - 500 GB / 465 GiB - WDC WD5000AACS-00G8B1 Disk /dev/mapper/bubba-storage - 2256 MB / 2152 MiB - WDC \ WD5000AACS-00G8B1 Disk /dev/dm-0 - 2256 MB / 2152 MiB - WDC WD5000AACS-00G8B1 [Proceed ] Please select the partition table type, press Enter when done. [Humax ] Humax partition table Hint: Humax partition table type has been detected. Disk /dev/sda - 500 GB / 465 GiB - WDC WD5000AACS-00G8B1 CHS 60801 255 63 - sector size=512 [ Analyse ] Disk /dev/sda - 500 GB / 465 GiB - CHS 60801 255 63 Current partition
Re: Resizing partitions on production environment
On Wed, Jul 08, 2009 at 10:42:14AM +0500, Daniel Suleyman wrote: Dear all, i have big issues. I've installed lenny on my server, installed all programs and ran it on production, ut now i need to install oracle on it. My artitions have sizes user:~# df -kh Filesystem Size Used Avail Use% Mounted on /dev/cciss/c0d0p1 327M 141M 170M 46% / tmpfs 5.9G 0 5.9G 0% /lib/init/rw udev 10M 104K 9.9M 2% /dev tmpfs 5.9G 0 5.9G 0% /dev/shm /dev/cciss/c0d0p9 80G 42G 35G 56% /home /dev/cciss/c0d0p8 373M 11M 343M 3% /tmp /dev/cciss/c0d0p5 4.6G 1.6G 2.9G 36% /usr /dev/cciss/c0d0p6 2.8G 1.2G 1.5G 45% /var and oracle wont install becouse my root partition have less size that oracle need. how I an resize my partitions on fly? or at least from livecd but with guaranteed no data losses. Thank you in advance, Daniel I've done this in the past when in a bind: If oracle wants to install to /opt/oracle, mkdir /home/oracle and then ln -s /home/oracle /opt/oracle This will put the oracle stuff in the /home partition. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Resizing partitions on production environment
Daniel Suleyman danik...@gmail.com writes: Dear all, i have big issues. I've installed lenny on my server, installed all programs and ran it on production, ut now i need to install oracle on it. and oracle wont install becouse my root partition have less size that oracle need. how I an resize my partitions on fly? or at least from livecd but with guaranteed no data losses. You can try gparted. http://gparted.sourceforge.net You can download GParted Live on CD there too. -- Regards, Paul Chany -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Resizing partitions on production environment
On Wed, Jul 08, 2009 at 10:42:14AM +0500, Daniel Suleyman wrote: and oracle wont install becouse my root partition have less size that oracle need. how I an resize my partitions on fly? or at least from livecd but with guaranteed no data losses. Thank you in advance, Daniel In any case, make a backup before you try anything. I probably won't try but repartition the disk(s) or add another disk and move / to the new disk. When you have the needed backup, you can as well repartition. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Resizing partitions on production environment
On Wed, Jul 8, 2009 at 3:38 PM, leel...@yun.yagibdah.de wrote: On Wed, Jul 08, 2009 at 10:42:14AM +0500, Daniel Suleyman wrote: and oracle wont install becouse my root partition have less size that oracle need. how I an resize my partitions on fly? or at least from livecd but with guaranteed no data losses. Thank you in advance, Daniel Oracle *probably* just wants to install to /opt. If it's possible, you could create a new filesystem and mount it as /opt. In any case, make a backup before you try anything. I probably won't try but repartition the disk(s) or add another disk and move / to the new disk. When you have the needed backup, you can as well repartition. ++ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- Noah Dain The beatings will continue, until morale improves - the Management -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Resizing partitions on production environment
ok, Ihave hardware raid, it make my life dificult or it will be transparent to the OS? I am installing oracle-xe-universal from sources.list it give me error no spce for /etc/dp?? (don't remember dir) I changed dpkg options setting instdir to /home/ but after oracle package outputed error cant find pre install script and post install script :( 2009/7/9 Noah Dain noahd...@gmail.com On Wed, Jul 8, 2009 at 3:38 PM, leel...@yun.yagibdah.de wrote: On Wed, Jul 08, 2009 at 10:42:14AM +0500, Daniel Suleyman wrote: and oracle wont install becouse my root partition have less size that oracle need. how I an resize my partitions on fly? or at least from livecd but with guaranteed no data losses. Thank you in advance, Daniel Oracle *probably* just wants to install to /opt. If it's possible, you could create a new filesystem and mount it as /opt. In any case, make a backup before you try anything. I probably won't try but repartition the disk(s) or add another disk and move / to the new disk. When you have the needed backup, you can as well repartition. ++ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- Noah Dain The beatings will continue, until morale improves - the Management -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Resizing partitions on production environment
If the filesystem allows for it, you can do it online. There, in line 389, is an example of howto grow xfs: http://sunoano.name/ws/public_xhtml/lvm.html#resizing_volumes pgpul0F7Q9xfp.pgp Description: PGP signature
Re: Resizing partitions on production environment
sorry forgot to cat fstab user:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc /proc proc defaults 0 0 /dev/cciss/c0d0p1 / ext3 errors=remount-ro 0 1 /dev/cciss/c0d0p9 /home ext3 defaults 0 2 /dev/cciss/c0d0p8 /tmp ext3 defaults 0 2 /dev/cciss/c0d0p5 /usr ext3 defaults 0 2 /dev/cciss/c0d0p6 /var ext3 defaults 0 2 /dev/cciss/c0d0p7 none swap sw 0 0 /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 2009/7/8 Suno Ano suno@sunoano.org If the filesystem allows for it, you can do it online. There, in line 389, is an example of howto grow xfs: http://sunoano.name/ws/public_xhtml/lvm.html#resizing_volumes
Re: Resizing partitions..
On Fri, 2002-06-28 at 22:01, Alex Malinovich wrote: parted is very safe. And it's actually quite easy to use. If you can use ftp (or any other pseudo-shell program) you'll be right at home in parted. And if you want to learn more about linux, using a Windows program such as PM won't help matters much will it? :) From GNU's parted webpage (http://www.gnu.org/software/parted/parted.html) under Features: For ext2, ext3 and reiserfs: the start of the partition must stay fixed. This would prevent me from doing what I had intended. Does this mean I must use Partition Magic, or do you know of other Linux-side tools? (I did a quick look, but discovered nothing substantial) Also, someone was telling me that if I wanted to resize the / partition I would have to boot to another partition (say, a floppy) and perform the operations while / was not mounted. Does this sound accurate? Exactly. And, actually, if you roll your own kernel The Debian Way, you won't even need to do that much. The package does it for you. You don't have it so bad now since your Windows partition is FAT32, so you can at least write the bootsect.lnx to it from linux. I had an NTFS partition, so I had to boot into windows anytime I recompiled my kernel. I'll never be able to get that Windows startup sound out of my head. :) Ouch, I can see why you switched. In an earlier post you had mentioned how odd it was to have /boot located where it was, and why - in that location - to have it at all. Those partitions were left from an earlier version of Red Hat that I was playing around with some time ago (before I installed woody), and that was its default/recommended disk setup. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On Sat, 2002-06-29 at 07:45, Andrew Biggadike wrote: From GNU's parted webpage (http://www.gnu.org/software/parted/parted.html) under Features: For ext2, ext3 and reiserfs: the start of the partition must stay fixed. This would prevent me from doing what I had intended. Does this mean I must use Partition Magic, or do you know of other Linux-side tools? (I did a quick look, but discovered nothing substantial) Yup. That's entirely true. The beginning of a ext2 partition MUST stay fixed for a RESIZE operation. A MOVE operation, on the other hand, is a completely different issue. :) Just move the partition down and then resize it up instead of the other way around. Also, someone was telling me that if I wanted to resize the / partition I would have to boot to another partition (say, a floppy) and perform the operations while / was not mounted. Does this sound accurate? Yes, that's correct. You can get a floppy boot disk with parted already on it on the parted home page. The official floppy images can be found at: ftp://ftp.gnu.org/gnu/parted/bootdisk/ You can find lots of other ones if you do a quick google search. In an earlier post you had mentioned how odd it was to have /boot located where it was, and why - in that location - to have it at all. Those partitions were left from an earlier version of Red Hat that I was playing around with some time ago (before I installed woody), and that was its default/recommended disk setup. You may want to just create a /boot on / and get rid of that partition. That's another 50 MB you can put on your ext2 partition. (And /boot should never really get much bigger than 4-5 MB.) -Alex signature.asc Description: This is a digitally signed message part
Re: Resizing partitions..
On 27 Jun 2002 21:37:53 -0400 Andrew Biggadike [EMAIL PROTECTED] wrote: Ah, yes, I did forget to mention: I am using NT Loader to dual boot, so I believe lilo is on /dev/hda3 (though I'm still not exactly clear about everything). Using the Windows loader shouldn't complicate matters at all, should it? You can check where lilo is installed by looking at the boot= entry in /etc/lilo.conf. The NT loader works fine, that's what I was using until yesterday. -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On Thu, 2002-06-27 at 20:37, Andrew Biggadike wrote: Ah, yes, I did forget to mention: I am using NT Loader to dual boot, so I believe lilo is on /dev/hda3 (though I'm still not exactly clear about everything). Using the Windows loader shouldn't complicate matters at all, should it? Sorry I got into this thread a bit late. Since it looks like you're already using Partition Magic, just an ethical heads up for future reference. With the exception of working with NTFS partitions, GNU parted, in my experience, works much better than PM as far as resizing goes. It's also a native linux app and is GPL'd therefore making it much more attractive from the ethical standpoint. And best of all, unlike PM, it won't butcher your partition numbers. Since you're using the NT Bootloader, you don't have to worry about your MBR while resizing. Since you're just going to be working with the tail end of hda1 nothing before that should be affected. Now, you said you wanted to take space from hda1 and add it to hda3 right? In this case you're going to need to resize hda1, then either move or resize hda2 (to get it next to hda1 again) and then resize hda3. I hope that makes sense. :) As long as all of your parition numbers remain the same, this shouldn't be an issue, though I'd make sure you have a boot disk handy either way. I used to use the NT Bootloader myself, but I got tired of needing to go through two loaders to get to linux so I just put lilo in the MBR. Just add: other=/dev/hda1 label=Windows -- or whatever you want the label to be to your /etc/lilo.conf. Hope this helps. :) -Alex signature.asc Description: This is a digitally signed message part
Re: Resizing partitions..
On Wednesday 26 June 2002 09:01 pm, Andrew Biggadike wrote: I have a laptop that's dual booting Windows 2000 and Debian (woody), and I want to resize my partitions so I can give some of the space on the Windows partition to Debian's /. Does anyone have any recommendations as to the best way to go about doing this? If I use a Windows tool, such as PartitionMagic, is it true that I won't have to modify anything within Linux in order for it to function properly? If not, what would I need to do? If I wanted to do it from Linux, how would I go about doing it? I guess the main thing, obviously, is that I don't want to break anything; I'd just like some more room to play with on this end. I've cleaned up and defragmented the Windows partition. Links to HOWTOs and other helpful documentation should be sufficient. Thanks, Andrew Oh, and in case it matters: hda1 FAT32 16861.83 hda2 Linux ext2 /boot 49.36 hda3 Linux ext2 / 2558.07 hda5 Linux swap 534.65 I use Partition Magic on dual-boot machines a lot, and it's always seemed to handle resizing ext2 and fat file systems just fine, without any extra tinkering needed on the Linux side. If you create or delete partitions things are likely to get a little more messy and you will need to tinker with lilo.conf and fstab to tell Linux where everything has moved to. The only possible weirdness I could see with your configuration is that /boot is not at the start of the disc, which is a setup I've never used. Gut instinct says it shouldn't be a problem, but I wouldn't bet my life (or critical data) on it. As ever, if it's important, back it up before tinkering with partitioning. - Derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On Wed, 2002-06-26 at 23:29, Derek Gladding wrote: The only possible weirdness I could see with your configuration is that /boot is not at the start of the disc, which is a setup I've never used. Gut instinct says it shouldn't be a problem, but I wouldn't bet my life (or critical data) on it. As ever, if it's important, back it up before tinkering with partitioning. Now that you mention it, that is rather odd. If /boot isn't at the beginning of the disk, why have it at all? The only time I use a seperate /boot partition is on old systems that have to deal with the 1024-cylinder boundary. -Alex signature.asc Description: This is a digitally signed message part
Re: Resizing partitions..
On Fri, 2002-06-28 at 12:46, Alex Malinovich wrote: Sorry I got into this thread a bit late. Since it looks like you're already using Partition Magic, just an ethical heads up for future reference. With the exception of working with NTFS partitions, GNU parted, in my experience, works much better than PM as far as resizing goes. It's also a native linux app and is GPL'd therefore making it much more attractive from the ethical standpoint. And best of all, unlike PM, it won't butcher your partition numbers. What exactly do you mean by butcher your partition numbers? I haven't done it yet and might like to try parted - not necessarily for ethical reasons (though I certainly understand what you're saying), but just to learn more about linux. My main concern is that I might mess it up, and the other way seems to be easier. Since you're using the NT Bootloader, you don't have to worry about your MBR while resizing. Since you're just going to be working with the tail end of hda1 nothing before that should be affected. Now, you said you wanted to take space from hda1 and add it to hda3 right? In this case you're going to need to resize hda1, then either move or resize hda2 (to get it next to hda1 again) and then resize hda3. I hope that makes sense. :) As long as all of your parition numbers remain the same, this shouldn't be an issue, though I'd make sure you have a boot disk handy either way. That's sort of what I had intended .. just shrinking hda1, sliding hda2 down, and giving the rest of the room to hda3. I'll definitely have a boot disk .. I used to use the NT Bootloader myself, but I got tired of needing to go through two loaders to get to linux so I just put lilo in the MBR. Just add: other=/dev/hda1 label=Windows -- or whatever you want the label to be to your /etc/lilo.conf. Hmm, I guess that would prevent me from having to `dd if=/dev/hda3 of=/bootsect.lnx bs=512 count=1` everytime I recompile the kernel, no? After I add those lines, would all I have to do is `lilo -b /dev/hda`? Thanks for all the info, Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On Fri, 2002-06-28 at 20:16, Andrew Biggadike wrote: What exactly do you mean by butcher your partition numbers? I haven't done it yet and might like to try parted - not necessarily for ethical reasons (though I certainly understand what you're saying), but just to learn more about linux. My main concern is that I might mess it up, and the other way seems to be easier. I don't know if this is still a problem, but the last time I used Partition Magic (I believe it was 5.0) it did everything that I wanted with no problem. Unfortunately, since it didn't ask me if I wanted partitions at the beginnings or ends of free space, I was left with a partition table vastly different from what I had planned out. Then again, I suppose that's more user error than anything. :) parted is very safe. And it's actually quite easy to use. If you can use ftp (or any other pseudo-shell program) you'll be right at home in parted. And if you want to learn more about linux, using a Windows program such as PM won't help matters much will it? :) Hmm, I guess that would prevent me from having to `dd if=/dev/hda3 of=/bootsect.lnx bs=512 count=1` everytime I recompile the kernel, no? After I add those lines, would all I have to do is `lilo -b /dev/hda`? Exactly. And, actually, if you roll your own kernel The Debian Way, you won't even need to do that much. The package does it for you. You don't have it so bad now since your Windows partition is FAT32, so you can at least write the bootsect.lnx to it from linux. I had an NTFS partition, so I had to boot into windows anytime I recompiled my kernel. I'll never be able to get that Windows startup sound out of my head. :) -Alex signature.asc Description: This is a digitally signed message part
Re: Resizing partitions..
Andrew Biggadike wrote: I have a laptop that's dual booting Windows 2000 and Debian (woody), and I want to resize my partitions so I can give some of the space on the Windows partition to Debian's /. Does anyone have any recommendations as to the best way to go about doing this? If I use a Windows tool, such as PartitionMagic, is it true that I won't have to modify anything within Linux in order for it to function properly? If not, what would I need to do? If I wanted to do it from Linux, how would I go about doing it? I guess the main thing, obviously, is that I don't want to break anything; I'd just like some more room to play with on this end. I've cleaned up and defragmented the Windows partition. Links to HOWTOs and other helpful documentation should be sufficient. Thanks, Andrew Oh, and in case it matters: hda1FAT32 16861.83 hda2Linux ext2 /boot 49.36 hda3Linux ext2 / 2558.07 hda5Linux swap 534.65 I am in this situation with the exception that my Windows 2000 partition is NTFS so I assumed off the bat that there wouldn't be a linux solution. I've resized by NTFS partition twice. My method was to just shrink the NTFS to create free space and then use nparted in linux to actually create the new partitions. I used Partition Magic. When you open it up, it(at least for me) will claim that the partition table has 'errors' and offer to fix them. You pretty much don't have a choice if you want to use the program so go along. In the process of fixing the errors, it will randomly renumber the partitions at which point you may or may not be able to boot into linux. Finish resizing the windows partition and try to reboot into linux(you may get lucky). If not boot from a rescue CD and fix /etc/fstab and /etc/lilo.conf and rerun lilo at which point you shouldn't have any problems... Though you may have significantly more options since your windows partition isn't NTFS... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On Wednesday 26 June 2002 09:59 pm, Travis Crump wrote: [snip] I am in this situation with the exception that my Windows 2000 partition is NTFS so I assumed off the bat that there wouldn't be a linux solution. I've resized by NTFS partition twice. My method was to just shrink the NTFS to create free space and then use nparted in linux to actually create the new partitions. I used Partition Magic. When you open it up, it(at least for me) will claim that the partition table has 'errors' and offer to fix them. Which version of Partition Magic are you using ? IIRC, there were some changes in NTFS in Win2K which confuse versions of Partition Magic lower than 7.0. - Derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
I have received those error messages when I have loaded up Partition Magic (7.0) as well - I haven't done anything yet though. You mentioned a rescue CD, how do I go about creating one? Is that a PartitionMagic rescue CD or a Linux rescue CD? Instead of creating new partitions, do you know if it is possible to shift the /boot and beginng of / down into the free space (thereby increasing the size of /)? Thanks for the info, Andrew On Thu, 2002-06-27 at 00:59, Travis Crump wrote: Andrew Biggadike wrote: I have a laptop that's dual booting Windows 2000 and Debian (woody), and I want to resize my partitions so I can give some of the space on the Windows partition to Debian's /. Does anyone have any recommendations as to the best way to go about doing this? If I use a Windows tool, such as PartitionMagic, is it true that I won't have to modify anything within Linux in order for it to function properly? If not, what would I need to do? If I wanted to do it from Linux, how would I go about doing it? I guess the main thing, obviously, is that I don't want to break anything; I'd just like some more room to play with on this end. I've cleaned up and defragmented the Windows partition. Links to HOWTOs and other helpful documentation should be sufficient. Thanks, Andrew Oh, and in case it matters: hda1FAT32 16861.83 hda2Linux ext2 /boot 49.36 hda3Linux ext2 / 2558.07 hda5Linux swap 534.65 I am in this situation with the exception that my Windows 2000 partition is NTFS so I assumed off the bat that there wouldn't be a linux solution. I've resized by NTFS partition twice. My method was to just shrink the NTFS to create free space and then use nparted in linux to actually create the new partitions. I used Partition Magic. When you open it up, it(at least for me) will claim that the partition table has 'errors' and offer to fix them. You pretty much don't have a choice if you want to use the program so go along. In the process of fixing the errors, it will randomly renumber the partitions at which point you may or may not be able to boot into linux. Finish resizing the windows partition and try to reboot into linux(you may get lucky). If not boot from a rescue CD and fix /etc/fstab and /etc/lilo.conf and rerun lilo at which point you shouldn't have any problems... Though you may have significantly more options since your windows partition isn't NTFS... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On 27 Jun 2002 00:01:43 -0400 Andrew Biggadike [EMAIL PROTECTED] wrote: I have a laptop that's dual booting Windows 2000 and Debian (woody), and I want to resize my partitions so I can give some of the space on the Windows partition to Debian's /. Does anyone have any I have a dual boot desktop PC, running Linux and Win2k Pro, and I already had to move/resize my partitions some 3 or 4 times. I've used Partition Magic 6, it understands Linux ext2fs and swap partitions, as well as Win2k partitions that aren't part of any dynamic disk. I had absolutely no problems on any of those runs. If I wanted to do it from Linux, how would I go about doing it? There's gnu parted (google's your friend), but the docs do not inspire a lot of confidence... seems like a still very young product. I guess the main thing, obviously, is that I don't want to break anything; I'd just like some more room to play with on this end. I've Whatever software you'll end up using, you *must* be prepared to reformat and reinstall everything on your machine. Any other expectation will very probably lead to grief. -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
On 27 Jun 2002 06:53:05 -0400 Andrew Biggadike [EMAIL PROTECTED] wrote: You mentioned a rescue CD, how do I go about creating one? Is that a PartitionMagic rescue CD or a Linux rescue CD? The Debian CDs can be used as rescue CDs. Otherwise, you can either download boot diskette images from Debian, or have rescue disks made by the mkboot command (debianutils package). Instead of creating new partitions, do you know if it is possible to shift the /boot and beginng of / down into the free space (thereby increasing the size of /)? You forgot to say how you have provided for the dual booting. Are you using lilo? grub? If lilo, is it on the mbr (/dev/hda) or on /dev/hda3? Anyway, if you have problems after moving/resizing the partitions, boot from the Debian CD, write linux root=/dev/hda3 at the lilo prompt, and you'll boot into linux. Then take whatever measures applicable (like running /sbin/lilo as root if you use lilo to boot). Luck, -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resizing partitions..
Ah, yes, I did forget to mention: I am using NT Loader to dual boot, so I believe lilo is on /dev/hda3 (though I'm still not exactly clear about everything). Using the Windows loader shouldn't complicate matters at all, should it? Thanks for the information! Andrew On Thu, 2002-06-27 at 18:28, Carlos Sousa wrote: The Debian CDs can be used as rescue CDs. Otherwise, you can either download boot diskette images from Debian, or have rescue disks made by the mkboot command (debianutils package). You forgot to say how you have provided for the dual booting. Are you using lilo? grub? If lilo, is it on the mbr (/dev/hda) or on /dev/hda3? Anyway, if you have problems after moving/resizing the partitions, boot from the Debian CD, write linux root=/dev/hda3 at the lilo prompt, and you'll boot into linux. Then take whatever measures applicable (like running /sbin/lilo as root if you use lilo to boot). Luck, -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: resizing partitions
parted and ext2resize. also, partition magic knows about ext2, so that's your easiest option. just get a partition magic bootdisk. DON'T use fips. wrong tool for the job. fips doesn't know how to split ext2 filesystems. only vfat and dos. pete On Sat 24 Mar 01, 1:06 PM, Michael P. Soulier said: Hey people. I've recently found out that my /tmp partition might be too small for a particular application. I know that fips is supposed to allow non-destructive repartitioning. How would you recommend such a thing under Linux? I don't have a windows partition, nor do I want one, so Partition Magic isn't an option. I'd just like to grow my /tmp partition a bit. Options? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED] With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Coffee... I've conquered the Borg on coffee! [EMAIL PROTECTED] -- Kathryn Janeway on the virtues of coffee www.dirac.org/p
Re: resizing partitions
on Sat, Mar 24, 2001 at 10:18:15AM -0800, Peter Jay Salzman ([EMAIL PROTECTED]) wrote: On Sat 24 Mar 01, 1:06 PM, Michael P. Soulier said: Hey people. I've recently found out that my /tmp partition might be too small for a particular application. I know that fips is supposed to allow non-destructive repartitioning. How would you recommend such a thing under Linux? I don't have a windows partition, nor do I want one, so Partition Magic isn't an option. I'd just like to grow my /tmp partition a bit. parted and ext2resize. also, partition magic knows about ext2, so that's your easiest option. just get a partition magic bootdisk. Have heard good things about parted (gparted?), but typically do the old fashioned thing of backing up partitions, repartitioning, and restoring to partitions. With the luxury of over-the-net archival (though I still keep current tape backups), this isn't terribly slow. Fact is that repartition-in-place *still* requires data backups for failure recovery. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpNn0GZ44W4h.pgp Description: PGP signature
