Re: root low space
The only problem I still have is to first backup home and root on another computer along my network. Obvious as it might be to most users, I found that dd if=/dev/vg1/root | ssh 192.168.#.## dd of=/home/chiendarret/tmp/vg1-root works fine with SystemRescueCD within my LAN. It is (also obviously) liable to file compression. francesco On Mon, May 26, 2014 at 8:04 AM, Francesco Pietra chiendar...@gmail.com wrote: I forgot to add that, either from the linux console, or a terminal from startx, fdisk -l shows correctly /dev/md0 /dev/md1, both with their /dev/mapper/vg1-root and all other /mapper/vg1 Also, all needed codes , resize2f lvreduce lvexternal are on the path. The only problem I still have is to first backup home and root on another computer along my network. francesco -- Forwarded message -- From: Francesco Pietra chiendar...@gmail.com Date: Sat, May 24, 2014 at 8:16 AM Subject: Re: root low space To: Adam Stiles a...@priceengines.co.uk Cc: amd64 Debian debian-amd64@lists.debian.org I first tried Parted Magic, as available from http://partedmagic.linuxfreedom.com/download.htm downloading the 2012_12-25_x86_64 version. Is that the same mentioned by Giacomo Mulas. Well, it recognizes immediately my boot partition /dev/md0 (ext2). As to unallocated /dev/md1, the scan brought to light four file systems, two for what are my /usr and /opt and two with mixed stuff. I was unable to try to backup my /vg1-root as from francesco@gig64:~$ *df -h* Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg1-root 922M 839M 35M 97% / udev 10M 0 10M 0% /dev tmpfs 1.6G 860K 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.2G 80K 3.2G 1% /run/shm /dev/mapper/vg1-home 770G 271G 461G 37% /home /dev/mapper/vg1-opt 9.1G 3.1G 5.6G 36% /opt /dev/mapper/vg1-tmp 5.4G 12M 5.1G 1% /tmp /dev/mapper/vg1-usr 55G 6.4G 46G 13% /usr /dev/mapper/vg1-var 19G 2.5G 15G 15% /var none 4.0K 0 4.0K 0% /sys/fs/cgroup francesco@gig64:~$ root@gig64:/home/francesco# cat */etc/fstab* # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc /proc proc defaults 0 0 /dev/mapper/vg1-root / ext3 errors=remount-ro 0 1 /dev/mapper/vg1-home /home ext3 defaults 0 2 /dev/mapper/vg1-opt /opt ext3 defaults 0 2 /dev/mapper/vg1-tmp /tmp ext3 defaults 0 2 /dev/mapper/vg1-usr /usr ext3 defaults 0 2 /dev/mapper/vg1-var /var ext3 defaults 0 2 /dev/mapper/vg1-swap none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 root@gig64:/home/francesco# xxx Then, I tried with systemrescuecd-x86-4.2.0 This too recognized immediately my /dev/md0 (ext2). However, a scan of the unallocated /dev/md1 (from gparted) resulted in The disk scan by gpart did not find any recognizable file systems on this disk xxx I assume I have taken a wrong way, both with PartedMagic and SystemRescueCD. Thanks for redirecting. I insist in trying to make room for vg1-root as a few months ago I succeeded in getting PCIExpress 3.0 for this ivybridge/GPU system, accelerating my MD simulations by some 15% with respect to PCIExpress 2.0. Unfortunately I did not take notice of how I did that. thanks francesco On Fri, May 23, 2014 at 11:42 AM, Adam Stiles a...@priceengines.co.uk wrote: On Friday 23 May 2014, Francesco Pietra wrote: In my case, described above, in order to be able to use # partclone.ext3 -c -d -s /dev/mapper/vg1-root -o /home/francesco/vg1-root.img how to first umount vg1-root? I was unable to do that correctly, so that partclone failed because device (/dev/map//vg1-root) is mounted at / thanks francesco (and sorry for such a low-level query) I just had to deal with a similar situation -- I ran out of space on the root file system while trying to do a dist-upgrade, leaving the package manager in a slightly broken state. Fortunately, I had another partition that I was able to shrink and so make more room for / . Just search online for system rescue CD. This is Gentoo-based, but don't let that put you off. It has an XFCE desktop, Midori web browser and -- what you need -- gparted. N.B. I strongly recommend powering your computer through a UPS while performing this operation! If you are unfortunate enough to lose power while in the middle of shrinking a partition, you probably will end up losing data. All good disk tools always try at least to keep the block map correct, by updating it piecemeal after copying each chunk of data; but when the power fails, you don't know for a fact that any write operation that had been in progress completed successfully
Re: root low space
It's cool dd if=/dev/vg1/root | ssh 192.168.#.## dd of=/home/chiendarret/tmp/vg1-root -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140602014648.78ffa...@mirrors.kernel.org
Re: root low space
I first tried Parted Magic, as available from http://partedmagic.linuxfreedom.com/download.htm downloading the 2012_12-25_x86_64 version. Is that the same mentioned by Giacomo Mulas. Well, it recognizes immediately my boot partition /dev/md0 (ext2). As to unallocated /dev/md1, the scan brought to light four file systems, two for what are my /usr and /opt and two with mixed stuff. I was unable to try to backup my /vg1-root as from francesco@gig64:~$ *df -h* Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg1-root 922M 839M 35M 97% / udev 10M 0 10M 0% /dev tmpfs 1.6G 860K 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.2G 80K 3.2G 1% /run/shm /dev/mapper/vg1-home 770G 271G 461G 37% /home /dev/mapper/vg1-opt 9.1G 3.1G 5.6G 36% /opt /dev/mapper/vg1-tmp 5.4G 12M 5.1G 1% /tmp /dev/mapper/vg1-usr 55G 6.4G 46G 13% /usr /dev/mapper/vg1-var 19G 2.5G 15G 15% /var none 4.0K 0 4.0K 0% /sys/fs/cgroup francesco@gig64:~$ root@gig64:/home/francesco# cat */etc/fstab* # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc /proc proc defaults 0 0 /dev/mapper/vg1-root / ext3 errors=remount-ro 0 1 /dev/mapper/vg1-home /home ext3 defaults 0 2 /dev/mapper/vg1-opt /opt ext3 defaults 0 2 /dev/mapper/vg1-tmp /tmp ext3 defaults 0 2 /dev/mapper/vg1-usr /usr ext3 defaults 0 2 /dev/mapper/vg1-var /var ext3 defaults 0 2 /dev/mapper/vg1-swap none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 root@gig64:/home/francesco# xxx Then, I tried with systemrescuecd-x86-4.2.0 This too recognized immediately my /dev/md0 (ext2). However, a scan of the unallocated /dev/md1 (from gparted) resulted in The disk scan by gpart did not find any recognizable file systems on this disk xxx I assume I have taken a wrong way, both with PartedMagic and SystemRescueCD. Thanks for redirecting. I insist in trying to make room for vg1-root as a few months ago I succeeded in getting PCIExpress 3.0 for this ivybridge/GPU system, accelerating my MD simulations by some 15% with respect to PCIExpress 2.0. Unfortunately I did not take notice of how I did that. thanks francesco On Fri, May 23, 2014 at 11:42 AM, Adam Stiles a...@priceengines.co.uk wrote: On Friday 23 May 2014, Francesco Pietra wrote: In my case, described above, in order to be able to use # partclone.ext3 -c -d -s /dev/mapper/vg1-root -o /home/francesco/vg1-root.img how to first umount vg1-root? I was unable to do that correctly, so that partclone failed because device (/dev/map//vg1-root) is mounted at / thanks francesco (and sorry for such a low-level query) I just had to deal with a similar situation -- I ran out of space on the root file system while trying to do a dist-upgrade, leaving the package manager in a slightly broken state. Fortunately, I had another partition that I was able to shrink and so make more room for / . Just search online for system rescue CD. This is Gentoo-based, but don't let that put you off. It has an XFCE desktop, Midori web browser and -- what you need -- gparted. N.B. I strongly recommend powering your computer through a UPS while performing this operation! If you are unfortunate enough to lose power while in the middle of shrinking a partition, you probably will end up losing data. All good disk tools always try at least to keep the block map correct, by updating it piecemeal after copying each chunk of data; but when the power fails, you don't know for a fact that any write operation that had been in progress completed successfully. -- AJS Price Engines Ltd. DDI: 01283 707058. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201405231042.52484.a...@priceengines.co.uk
Re: root low space
In my case, described above, in order to be able to use # partclone.ext3 -c -d -s /dev/mapper/vg1-root -o /home/francesco/vg1-root.img how to first umount vg1-root? I was unable to do that correctly, so that partclone failed because device (/dev/map//vg1-root) is mounted at / thanks francesco (and sorry for such a low-level query) On Thu, May 22, 2014 at 7:30 PM, Giacomo Mulas gmu...@oa-cagliari.inaf.itwrote: On Thu, 22 May 2014, Francesco Pietra wrote: no mention about ext3, which is the filesystem I use (ext2 only for boot). you should use the lines below, where it says if you prefer to do this manually..., it applies also to ext3. Do have a look at the manpages for resize2fs and lvreduce, to find out the appropriate command line options for your case. Very generally, when you want to reduce a volume you first reduce the filesystem, then reduce the volume; when you want to enlarge it, you first enlarge the lvm volume, then you can expand the filesystem. The tools that you use for shrinking/expanding the filesystem depend on the filesystem, and are different for ext2/3/4, reiser, xfs... but you can usually look them up easily on google. In your case, since you need to boot off a live distro, make sure the live distro has all the tools you need installed and working, which for you are resize2fs, lvreduce and lvextend. Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _
Re: root low space
On Fri, 23 May 2014, Francesco Pietra wrote: In my case, described above, in order to be able to use # partclone.ext3 -c -d -s /dev/mapper/vg1-root -o /home/francesco/vg1-root.img how to first umount vg1-root? I was unable to do that correctly, so that partclone failed because device (/dev/map//vg1-root) is mounted at / As I told you before, you will have to boot that machine off a cd, dvd, usb stick. You should therefore select a live distribution (that can be installed and booted from such a medium) and use that. Be sure to select a live distro that includes the tools you need. As I told you before, I used parted magic, but it is not free anymore (even if cheap, and it does provide all the tools you will need for offline disk maintenance). A live Debian, Ubuntu, or any other major distro would probably be ok as well. Just choose one you are comfortable with. E.g. you may try looking at http://live.debian.net/ and https://www.debian.org/CD/live/ for debian live images Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _
Re: root low space
On Friday 23 May 2014, Francesco Pietra wrote: In my case, described above, in order to be able to use # partclone.ext3 -c -d -s /dev/mapper/vg1-root -o /home/francesco/vg1-root.img how to first umount vg1-root? I was unable to do that correctly, so that partclone failed because device (/dev/map//vg1-root) is mounted at / thanks francesco (and sorry for such a low-level query) I just had to deal with a similar situation -- I ran out of space on the root file system while trying to do a dist-upgrade, leaving the package manager in a slightly broken state. Fortunately, I had another partition that I was able to shrink and so make more room for / . Just search online for system rescue CD. This is Gentoo-based, but don't let that put you off. It has an XFCE desktop, Midori web browser and -- what you need -- gparted. N.B. I strongly recommend powering your computer through a UPS while performing this operation! If you are unfortunate enough to lose power while in the middle of shrinking a partition, you probably will end up losing data. All good disk tools always try at least to keep the block map correct, by updating it piecemeal after copying each chunk of data; but when the power fails, you don't know for a fact that any write operation that had been in progress completed successfully. -- AJS Price Engines Ltd. DDI: 01283 707058. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201405231042.52484.a...@priceengines.co.uk
Re: root low space
Hi Francesco, backup only the affected volumes (2 in your case, being vg1-root and vg1-home). A tool like partclone can be useful in your case, as it only backups used sectors, which reduces file size of the resulting backup image and also speeds up the whole process. Greets Robert Am 22.05.2014 08:43, schrieb Francesco Pietra: Do you mean backing up the volume being affected or all partitions/ thanks francesco On Thu, May 22, 2014 at 3:45 AM, Hendrik Boom hend...@topoi.pooq.com mailto:hend...@topoi.pooq.com wrote: On Wed, May 21, 2014 at 09:05:50PM +0200, Francesco Pietra wrote: Hi Robert: Thanks for the input. I was at older ideas that shrinking a volume is a dangerous move. francesco Just in case, make a backup first! -- hendr8ik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org mailto:debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: https://lists.debian.org/20140522014546.gb27...@topoi.pooq.com -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/537da06e.4030...@rinx.de
Re: root low space
On Wed, 21 May 2014, Francesco Pietra wrote: Hi Robert: Thanks for the input. I was at older ideas that shrinking a volume is a dangerous move. it still is, to some extent: if for whatever reason a resizing is aborted midway (e.g. a power outage, an unrelated kernel panic...) all the contents of the filesystem being resized are lost. Since these are hopefully unlikely events, it's a remote possibility, but a catastrophic one. Do make sure to have up to date backups before resizing a filesystem containing important data. And restrain your dog from playing with the power cord while resizing :) Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.10.1405220952480.25...@capitanata.oa-cagliari.inaf.it
Re: root low space
Giacomo: As I told you, my pointing dog has left. His performance in Gonnascodina on partridges remains in the records of the referee that had the luck of refereeing that game. Also, my The Old Man and the Roading Dog on Gray's Sporting Journal, 2005, 30(4), 13, was substantially the record of another performance of that dog, at which I was alone. Moreover, I use to maintain the same my home on my two amd64 raid-mirror boxes, wheezy and jelly. So, the only concern - as far as I understand - is the root partition. Thanks for your recommendations francesco On Thu, May 22, 2014 at 9:59 AM, Giacomo Mulas gmu...@oa-cagliari.inaf.itwrote: On Wed, 21 May 2014, Francesco Pietra wrote: Hi Robert: Thanks for the input. I was at older ideas that shrinking a volume is a dangerous move. it still is, to some extent: if for whatever reason a resizing is aborted midway (e.g. a power outage, an unrelated kernel panic...) all the contents of the filesystem being resized are lost. Since these are hopefully unlikely events, it's a remote possibility, but a catastrophic one. Do make sure to have up to date backups before resizing a filesystem containing important data. And restrain your dog from playing with the power cord while resizing :) Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _
Re: root low space
Hi Robert; Could you be so kind to provide - at your convenience - some detail on the commands needed, or give a link? I imagine that umount and mount are needed I executed the following commands, retaining the output: 1) francesco@gig64:~$ df -h 2) root@gig64:/home/francesco# fdisk -l 3) root@gig64:/home/francesco# cat /etc/fstab 4) # touch /forcefsk followed by # shutdown -h now and by booting again, as I guess that the partitions should be clean. Has the created file /forcefsk to be removed to prevent disk checking at any reboot? The system is warning about low space so that I can't delay a remedy. I do rarely disk maintenance, so that the little I know flies in part away between arepar and the next one. Thanks a lot francesco On Thu, May 22, 2014 at 8:59 AM, Robert Rottscholl secur...@rinx.de wrote: Hi Francesco, backup only the affected volumes (2 in your case, being vg1-root and vg1-home). A tool like partclone can be useful in your case, as it only backups used sectors, which reduces file size of the resulting backup image and also speeds up the whole process. Greets Robert Am 22.05.2014 08:43, schrieb Francesco Pietra: Do you mean backing up the volume being affected or all partitions/ thanks francesco On Thu, May 22, 2014 at 3:45 AM, Hendrik Boom hend...@topoi.pooq.com mailto:hend...@topoi.pooq.com wrote: On Wed, May 21, 2014 at 09:05:50PM +0200, Francesco Pietra wrote: Hi Robert: Thanks for the input. I was at older ideas that shrinking a volume is a dangerous move. francesco Just in case, make a backup first! -- hendr8ik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org mailto:debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: https://lists.debian.org/20140522014546.GB27467@topoi. pooq.com -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/537da06e.4030...@rinx.de
Re: root low space
On Thu, 22 May 2014, Francesco Pietra wrote: Hi Robert; Could you be so kind to provide - at your convenience - some detail on the commands needed, or give a link? I imagine that umount and mount are needed You can find most of what you need here: http://tldp.org/HOWTO/LVM-HOWTO/commontask.html look at reducing a logical volume to see how to reduce some other volume (e.g. home) to make some additional room for your root, then extending a logical volume to extend your root. Note that in most cases (e.g. unless you are using btrfs which must be resized while mounted) filesystems must be unmounted to be resized. This means that you will have to boot your computer from a some live media, so that you can operate on the root filesystem. For this kind of tasks I used to use parted magic, booting from a usb stick. I see that it has become a commercial product now, so I guess you can use any functional live linux distro which includes lvm and resize2fs. However, since it's cheap (5 US$) you may still want to try parted magic and keep it around as a convenient toolchest for offline maintenance of disks, partitions, arrays etc. Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.10.1405221720490.11...@capitanata.oa-cagliari.inaf.it
Re: root low space
On Thu, May 22, 2014 at 08:43:30AM +0200, Francesco Pietra wrote: Do you mean backing up the volume being affected or all partitions/ thanks francesco In theory, it should be sufficient to back up the volumes baing affected. But I always back up everything, just in case I do something wrong and destroy somthing else. -- hendrik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140522164817.ga6...@topoi.pooq.com
Re: root low space
Hi Giacomo: On the link you provided: ext2 If you are using LVM 1 with ext2 as the file system then you can use the e2fsadm command mentioned earlier to take care of both the file system and volume resizing as follows: # umount /home # e2fsadm -L-1G /dev/myvg/homevol # mount /home no mention about ext3, which is the filesystem I use (ext2 only for boot). In contrast. ext2/ext3 for expanding. thanks francesco On Thu, May 22, 2014 at 5:37 PM, Giacomo Mulas gmu...@oa-cagliari.inaf.itwrote: On Thu, 22 May 2014, Francesco Pietra wrote: Hi Robert; Could you be so kind to provide - at your convenience - some detail on the commands needed, or give a link? I imagine that umount and mount are needed You can find most of what you need here: http://tldp.org/HOWTO/LVM-HOWTO/commontask.html look at reducing a logical volume to see how to reduce some other volume (e.g. home) to make some additional room for your root, then extending a logical volume to extend your root. Note that in most cases (e.g. unless you are using btrfs which must be resized while mounted) filesystems must be unmounted to be resized. This means that you will have to boot your computer from a some live media, so that you can operate on the root filesystem. For this kind of tasks I used to use parted magic, booting from a usb stick. I see that it has become a commercial product now, so I guess you can use any functional live linux distro which includes lvm and resize2fs. However, since it's cheap (5 US$) you may still want to try parted magic and keep it around as a convenient toolchest for offline maintenance of disks, partitions, arrays etc. Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _
Re: root low space
On Thu, 22 May 2014, Francesco Pietra wrote: no mention about ext3, which is the filesystem I use (ext2 only for boot). you should use the lines below, where it says if you prefer to do this manually..., it applies also to ext3. Do have a look at the manpages for resize2fs and lvreduce, to find out the appropriate command line options for your case. Very generally, when you want to reduce a volume you first reduce the filesystem, then reduce the volume; when you want to enlarge it, you first enlarge the lvm volume, then you can expand the filesystem. The tools that you use for shrinking/expanding the filesystem depend on the filesystem, and are different for ext2/3/4, reiser, xfs... but you can usually look them up easily on google. In your case, since you need to boot off a live distro, make sure the live distro has all the tools you need installed and working, which for you are resize2fs, lvreduce and lvextend. Ciao Giacomo -- _ Giacomo Mulas gmu...@oa-cagliari.inaf.it _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180244 mob. : +39 329 6603810 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.10.1405221921580.13...@capitanata.oa-cagliari.inaf.it
Re: root low space
Hi Robert: Thanks for the input. I was at older ideas that shrinking a volume is a dangerous move. francesco On Tue, May 20, 2014 at 9:00 PM, Robert Rottscholl secur...@rinx.de wrote: Hi Fransesco, what does 'vgs' say is there free space? If not, resize vg1-home (reduce size) and afterwards increase vg1-root. But be careful first resize the filesystem (resize2fs) and afterwards the logical volume (lvreduce), otherwise you might loose data. Regards Robert Rottscholl Am 20.05.2014 19:24, schrieb Francesco Pietra: Hello: I was short seeing in building my partitions for raid mirror with jelly (two disks 1000 MB each) With latest upgrading francesco@gig64:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg1-root 922M 839M 35M 97% / udev 10M 0 10M 0% /dev tmpfs 1.6G 860K 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.2G 80K 3.2G 1% /run/shm /dev/mapper/vg1-home 770G 248G 484G 34% /home /dev/mapper/vg1-opt 9.1G 3.1G 5.6G 36% /opt /dev/mapper/vg1-tmp 5.4G 13M 5.1G 1% /tmp /dev/mapper/vg1-usr55G 6.4G 46G 13% /usr /dev/mapper/vg1-var19G 2.5G 15G 15% /var none 4.0K 0 4.0K 0% /sys/fs/cgroup francesco@gig64:~$ I fear ther is no possibility to expand vg1-root. Or is any? There are troublesome installations besides the norm, so it would be worthwhile to find a way. Thanks for advice francesco pietra -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/537ba645.3020...@rinx.de
Re: root low space
On Wed, May 21, 2014 at 09:05:50PM +0200, Francesco Pietra wrote: Hi Robert: Thanks for the input. I was at older ideas that shrinking a volume is a dangerous move. francesco Just in case, make a backup first! -- hendr8ik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140522014546.gb27...@topoi.pooq.com
Re: root low space
Hi Fransesco, what does 'vgs' say is there free space? If not, resize vg1-home (reduce size) and afterwards increase vg1-root. But be careful first resize the filesystem (resize2fs) and afterwards the logical volume (lvreduce), otherwise you might loose data. Regards Robert Rottscholl Am 20.05.2014 19:24, schrieb Francesco Pietra: Hello: I was short seeing in building my partitions for raid mirror with jelly (two disks 1000 MB each) With latest upgrading francesco@gig64:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg1-root 922M 839M 35M 97% / udev 10M 0 10M 0% /dev tmpfs 1.6G 860K 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.2G 80K 3.2G 1% /run/shm /dev/mapper/vg1-home 770G 248G 484G 34% /home /dev/mapper/vg1-opt 9.1G 3.1G 5.6G 36% /opt /dev/mapper/vg1-tmp 5.4G 13M 5.1G 1% /tmp /dev/mapper/vg1-usr55G 6.4G 46G 13% /usr /dev/mapper/vg1-var19G 2.5G 15G 15% /var none 4.0K 0 4.0K 0% /sys/fs/cgroup francesco@gig64:~$ I fear ther is no possibility to expand vg1-root. Or is any? There are troublesome installations besides the norm, so it would be worthwhile to find a way. Thanks for advice francesco pietra -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/537ba645.3020...@rinx.de
