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
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:
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
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
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
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
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
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
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
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
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)
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:
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
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
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
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
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
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%
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
19 matches
Mail list logo
