LVM + XFS/Ext3 (Was no space left on device: LVM, Gnus -- dpkg, apt-get ?)
On 4 Jan 2002, Karl M. Hegbloom wrote: I'm using LVM and XFS filesystems on my computer at home. This morning, after I pushed g from the Gnus *Group* buffer (to get new mail), it stopped part way through with an error message. Gnus prompted me in the XEmacs minibuffer saying no space left on device: Continue (yes, no)?. My 10g /home logical volume had filled up. I opened a root console, used lvextend to add a few spare gigs to my /home LV, then ran xfs_growfs to grow it's filesystem into the new space. I just installed my new 80GB disk using LVM. I found out that it is not possible to include even /boot and / partition into LVM if you want to use grub, but this is no real problem (even if it would be nice). I decided to use ext3 file systems in the LVM partitions and I wonder if there is something like xfs_growfs for ext[23]. Not that I would need it currently but just in case it is better to know now and to switch to XFS at this moment than later if it is not possible. Kind regards Andreas.
Re: LVM + XFS/Ext3 (Was no space left on device: LVM, Gnus -- dpkg,apt-get ?)
[...] I decided to use ext3 file systems in the LVM partitions and I wonder if there is something like xfs_growfs for ext[23]. Not that I would I made som very basic test on this some some weeks ago, and I extended an ext3(2?) fs sucessfully (i.e. the data was intact after the expansion). If I recall correctly you can extend the filesystem more or less in use but you have to unmount it to reduce it. I should say that although the filesystem was mounted during extension there was no real usage of it (no fileaccess). Best regards, Emil
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
On 06-Jan-02, 01:51 (CST), Egon Willighagen [EMAIL PROTECTED] wrote: Now, I am facing the following problem (after making more space): - how can i determine which packages were updated yesterday? - how can i (semi)-automatically reinstall these packages? I see that it turned out that the problem was different, but what I've done in similar circumstances is 'find' to list all the directories in /usr/share/doc that have been updated in _time period_, and feed the output to 'apt-get --reinstall install'. Steve
Re: LVM + XFS/Ext3 (Was no space left on device: LVM, Gnus -- dpkg, apt-get ?)
Andreas == Andreas Tille Tille writes: Andreas On 4 Jan 2002, Karl M. Hegbloom wrote: I'm using LVM and XFS filesystems on my computer at home. This morning, after I pushed g from the Gnus *Group* buffer (to get new mail), it stopped part way through with an error message. Gnus prompted me in the XEmacs minibuffer saying no space left on device: Continue (yes, no)?. My 10g /home logical volume had filled up. I opened a root console, used lvextend to add a few spare gigs to my /home LV, then ran xfs_growfs to grow it's filesystem into the new space. I have not tried yet, but am planning to experiment and see if it is possible to *shrink* an XFS filesystem. In the case where I have one LV that's larger than it needed to be, I'd like to be able to shrink the filesystem then shrink the LV. Anyone know if that is possible? If it's not, it should be! Andreas I just installed my new 80GB disk using LVM. I found out Andreas that it is not possible to include even /boot and / Andreas partition into LVM if you want to use grub, but this is Andreas no real problem (even if it would be nice). Right. I went with: part1 500m Linux / (XFS) part2 1024m Swap part3 the rest LVM/usr (XFS) /home /var /usr/local /usr/local/src Andreas I decided to use ext3 file systems in the LVM partitions Andreas and I wonder if there is something like xfs_growfs for Andreas ext[23]. Not that I would need it currently but just in Andreas case it is better to know now and to switch to XFS at Andreas this moment than later if it is not possible. I recently read Linux File Systems, by Moshe Bar (author of Linux Internals), Osbourne McGraw Hill, ISBN-0-07-212955-7. I also read Journal File Systems, Linux Gazette #55, URL:http://www.linuxgazette.com/issue55/florido.html, and some of the whitepapers I found at URL:http://oss.sgi.com/projects/xfs/. I am very convinced that XFS is the *best* filesystem for Linux. It is way better than ext3fs for many reasons. From what I gather, it is also superiour to IBM's JFS, and certainly superiour to Reiserfs. I've had no trouble with it so far. I've been told that it is incompatible with LILO; that it starts the filesystem at offset 0 rather than offset 512 like other filesystems? I have not confirmed this yet. Anyone know? It works great with GRUB. -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] Free the Software http://www.debian.org/social_contract http://www.microsharp.com phone://USA/WA/360-260-2066
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
Adrian == Adrian Bunk [EMAIL PROTECTED] writes:
Adrian On Sun, 6 Jan 2002, Egon Willighagen wrote:
...
That makes me wonder: is it possible that i am imagening things, and
that the
upgrade went well, even though my HD was full? Did it actually install
files
then, or did it not overwrite, because of the HD being full, and my
files are
basically not upgraded, but just the version numbers in the index that
dpkg
uses?
Adrian Do you mean with my HD was full that df says that it's used
100% ?
Adrian If yes then your HD isn't physically full, usually 5% of the blocks
in a
Adrian partition are reserved - this means they aren't counted when df
Adrian estimates how many space is free on the device and only root can
write to
Adrian the device if not more than the number of reserved blocks are free.
Since
Adrian you did run dpkg as root you can write additional files to the
partition
Adrian even though the partition is full.
If I understand correctly, this is filesystem implementation
dependant. It is certainly true for ext{2,3}fs. What about the
others, I wonder? This should be looked into, and perhaps documented
in a paragraph of man mkfs.
--
mailto: (Karl M. Hegbloom) [EMAIL PROTECTED]
Free the Software http://www.debian.org/social_contract
http://www.microsharp.com
phone://USA/WA/360-260-2066
Re: LVM + XFS/Ext3 (Was no space left on device: LVM, Gnus -- dpkg, apt-get ?)
Tille, Andreas [EMAIL PROTECTED] wrote:
I decided to use ext3 file systems in the LVM partitions and I wonder
if there is something like xfs_growfs for ext[23]. Not that I would
apt-get install ext2resize
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: LVM + XFS/Ext3 (Was no space left on device: LVM, Gnus -- dpkg, apt-get ?)
On Tue, Jan 08, 2002 at 09:59:45AM -0800, Karl M. Hegbloom wrote: I have not tried yet, but am planning to experiment and see if it is possible to *shrink* an XFS filesystem. In the case where I have one LV that's larger than it needed to be, I'd like to be able to shrink the filesystem then shrink the LV. Anyone know if that is possible? If it's not, it should be! It is not possible to shrink XFS filesystems. I am very convinced that XFS is the *best* filesystem for Linux. It is way better than ext3fs for many reasons. From what I gather, it is also superiour to IBM's JFS, and certainly superiour to Reiserfs. I felt the same way, up until a couple of months ago. I had been running only XFS on my laptop for a good 6 months or so, when suddenly very weird things started happening. Files and directories would randomly become inaccessable, hanging any command that touched them. My attempts to fix the problems lead to even more frustration. xfs_repair cannot be run unless the filesystem is completely unmounted. This is, shall we say, a major pain when your root fs is XFS. I ended up completely reinstalling, and am currently running only ext2. Not that I think ext2 is a particularly good filesystem, but it's certainly the most mature at this point. I've had no trouble with it so far. I've been told that it is incompatible with LILO; that it starts the filesystem at offset 0 rather than offset 512 like other filesystems? I have not confirmed this yet. Anyone know? It works great with GRUB. LILO and XFS are fine together. In fact, it wasn't until fairly recently that GRUB could boot from XFS. For the longest time I had to use LILO because GRUB couldn't read my XFS filesystems. noah -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html pgpkdlPSGcd5n.pgp Description: PGP signature
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
On Sunday 6 January 2002 12:09, Adrian Bunk wrote: On Sun, 6 Jan 2002, Egon Willighagen wrote: ... That makes me wonder: is it possible that i am imagening things, and that the upgrade went well, even though my HD was full? Did it actually install files then, or did it not overwrite, because of the HD being full, and my files are basically not upgraded, but just the version numbers in the index that dpkg uses? Do you mean with my HD was full that df says that it's used 100% ? If yes then your HD isn't physically full, usually 5% of the blocks in a partition are reserved - this means they aren't counted when df estimates how many space is free on the device and only root can write to the device if not more than the number of reserved blocks are free. Since you did run dpkg as root you can write additional files to the partition even though the partition is full. Ah great! Thanx for the info! Egon
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
On Sunday 6 January 2002 08:51, Egon Willighagen wrote: On Saturday 5 January 2002 00:24, Karl M. Hegbloom wrote: Wow, now that's really cool. What I'm wondering is, can apt-get, dpkg, and friends recover this easily from a device overflow? Was that thought of during their design and implementation? If it needs a little more space in /var or /usr, can it notice that before filling the block device, and prompt me about it, so I can make some room somehow? (either by removing files, dpkg --purging something, or using the LVM tools to extend the logical volume and then the filesystem utility to grow the filesystem.) That is funny. I had just this problem yesterday... I apt-get upgrade-ed and my HD was full... and now my system is in dubious state... Missing KDE icons. Or actually, i think this is caused by a versioning problem that is caused by the upgrade: libpng warning: Application was compiled with png.h from libpng-1.0.12 libpng warning: Application is running with png.c from libpng-1.2.1 libpng error: Incompatible libpng version in application and library I guess packages are only partly upgraded. Some files are, others are not... I can only fear what other incompatibilities are caused by the upgrade. Actually, i have just read a debian-kde message about the PNG problem... That seems to be a KDE specific problem. That makes me wonder: is it possible that i am imagening things, and that the upgrade went well, even though my HD was full? Did it actually install files then, or did it not overwrite, because of the HD being full, and my files are basically not upgraded, but just the version numbers in the index that dpkg uses? Egon
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
On Saturday 5 January 2002 00:24, Karl M. Hegbloom wrote: Wow, now that's really cool. What I'm wondering is, can apt-get, dpkg, and friends recover this easily from a device overflow? Was that thought of during their design and implementation? If it needs a little more space in /var or /usr, can it notice that before filling the block device, and prompt me about it, so I can make some room somehow? (either by removing files, dpkg --purging something, or using the LVM tools to extend the logical volume and then the filesystem utility to grow the filesystem.) That is funny. I had just this problem yesterday... I apt-get upgrade-ed and my HD was full... and now my system is in dubious state... Missing KDE icons. Or actually, i think this is caused by a versioning problem that is caused by the upgrade: libpng warning: Application was compiled with png.h from libpng-1.0.12 libpng warning: Application is running with png.c from libpng-1.2.1 libpng error: Incompatible libpng version in application and library I guess packages are only partly upgraded. Some files are, others are not... I can only fear what other incompatibilities are caused by the upgrade. Now, I am facing the following problem (after making more space): - how can i determine which packages were updated yesterday? - how can i (semi)-automatically reinstall these packages? In the mean time i filed a bug (#127942) against apt for loss of non-critical data. It can be argued wether it is loss or not, but anyway, my systems expects files that are not installed, and thus are missing IMHO... Egon
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
On Sun, 6 Jan 2002, Egon Willighagen wrote: ... That makes me wonder: is it possible that i am imagening things, and that the upgrade went well, even though my HD was full? Did it actually install files then, or did it not overwrite, because of the HD being full, and my files are basically not upgraded, but just the version numbers in the index that dpkg uses? Do you mean with my HD was full that df says that it's used 100% ? If yes then your HD isn't physically full, usually 5% of the blocks in a partition are reserved - this means they aren't counted when df estimates how many space is free on the device and only root can write to the device if not more than the number of reserved blocks are free. Since you did run dpkg as root you can write additional files to the partition even though the partition is full. Egon cu Adrian
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
Egon Willighagen wrote: That makes me wonder: is it possible that i am imagening things, and that the upgrade went well, even though my HD was full? Did it actually install files then, or did it not overwrite, because of the HD being full, and my files are basically not upgraded, but just the version numbers in the index that dpkg uses? Dpkg has very robust error detection and handling code. If the disk fills up or it cannot write to a file, it will abort the upgrade, and roll back to the previously installed version of the package. It doesn't have support for pausing for more disk space to be made available, but then all you have to do is run it again.. -- see shy jo
Re: no space left on device: LVM, Gnus -- dpkg, apt-get ?
Egon Willighagen [EMAIL PROTECTED] sbagliò: Actually, i have just read a debian-kde message about the PNG problem... That seems to be a KDE specific problem. Yes, it is due to the problem about libpng. Apt is completely innocent. :-) -- Au revoir. Lele...
no space left on device: LVM, Gnus -- dpkg, apt-get ?
I'm using LVM and XFS filesystems on my computer at home. This morning, after I pushed g from the Gnus *Group* buffer (to get new mail), it stopped part way through with an error message. Gnus prompted me in the XEmacs minibuffer saying no space left on device: Continue (yes, no)?. My 10g /home logical volume had filled up. I opened a root console, used lvextend to add a few spare gigs to my /home LV, then ran xfs_growfs to grow it's filesystem into the new space. I then went back to XEmacs, typed yes to the question, and watched while it happily finished tossing all of my mail into folders. It is actually coded in such a way that it can gracefully deal with this situation! (Had I said no there, it would have left my mail in the crashbox, safe and sound.) Wow, now that's really cool. What I'm wondering is, can apt-get, dpkg, and friends recover this easily from a device overflow? Was that thought of during their design and implementation? If it needs a little more space in /var or /usr, can it notice that before filling the block device, and prompt me about it, so I can make some room somehow? (either by removing files, dpkg --purging something, or using the LVM tools to extend the logical volume and then the filesystem utility to grow the filesystem.) -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] http://www.microsharp.com phone://USA/WA/360-260-2066 jabber: [EMAIL PROTECTED]
