[gentoo-user] /boot without space.

[gentoo-user] /boot without space.

[Ricardo Bevilacqua]

I was installing a boot splash when i got this message

//////////////////////
o Creating initramfs image..
mv: writing «/boot/fbsplash-livecd-2007.0-1024x768»: There is no space
left on the device.
//////////////////////

I was surprised so I checked the /boot partition

/////////////////////
tux boot # ls -l
total 6939
lrwxrwxrwx 1 root root       1 may  2 20:26 boot -> .
lrwxrwxrwx 1 root root      23 may 14 16:24 config -> config-2.6.20-gentoo-r7
-rw-r--r-- 1 root root   42747 may 14 16:24 config-2.6.20-gentoo-r7
-rw------- 1 root root    8192 jun 21 17:56 fbsplash-livecd-2007.0-1024x768
-rw-r--r-- 1 root root 3001456 jun 21 16:44 gentoo-2.6.20
drwxr-xr-x 2 root root     632 may  3 15:42 grub
lrwxrwxrwx 1 root root      27 may 14 16:24 System.map ->
System.map-2.6.20-gentoo-r7
-rw-r--r-- 1 root root 1012133 may 14 16:24 System.map-2.6.20-gentoo-r7
lrwxrwxrwx 1 root root      24 may 14 16:24 vmlinuz -> vmlinuz-2.6.20-gentoo-r7
-rw-r--r-- 1 root root   57344 jun 21 16:44 vmlinuz-2.6.20-gentoo-r7
-rw-r--r-- 1 root root 2969600 jun 21 16:06 vmlinuz-2.6.20-gentoo-r7.old
////////////////////

Here I just have ~7Mb.
Inside /boot/grub I have much less than 1Mb.

Since the boot partition has 40Mb, why does my system say that is full
if I only see less than 8Mb?

////////////////////
tux grub # df -h | grep boot
/dev/hdc1              40M   40M     0 100% /boot
////////////////////

Thanks in advance.

Richard.
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Hemmann, Volker Armin]

On Donnerstag, 21. Juni 2007, Ricardo Bevilacqua wrote:
> I was installing a boot splash when i got this message
>
> //////////////////////
> o Creating initramfs image..
> mv: writing «/boot/fbsplash-livecd-2007.0-1024x768»: There is no space
> left on the device.
> //////////////////////
>
> I was surprised so I checked the /boot partition
>
> /////////////////////
> tux boot # ls -l
> total 6939
> lrwxrwxrwx 1 root root       1 may  2 20:26 boot -> .
> lrwxrwxrwx 1 root root      23 may 14 16:24 config ->
> config-2.6.20-gentoo-r7 -rw-r--r-- 1 root root   42747 may 14 16:24
> config-2.6.20-gentoo-r7 -rw------- 1 root root    8192 jun 21 17:56
> fbsplash-livecd-2007.0-1024x768 -rw-r--r-- 1 root root 3001456 jun 21 16:44
> gentoo-2.6.20
> drwxr-xr-x 2 root root     632 may  3 15:42 grub
> lrwxrwxrwx 1 root root      27 may 14 16:24 System.map ->
> System.map-2.6.20-gentoo-r7
> -rw-r--r-- 1 root root 1012133 may 14 16:24 System.map-2.6.20-gentoo-r7
> lrwxrwxrwx 1 root root      24 may 14 16:24 vmlinuz ->
> vmlinuz-2.6.20-gentoo-r7 -rw-r--r-- 1 root root   57344 jun 21 16:44
> vmlinuz-2.6.20-gentoo-r7 -rw-r--r-- 1 root root 2969600 jun 21 16:06
> vmlinuz-2.6.20-gentoo-r7.old ////////////////////
>
> Here I just have ~7Mb.
> Inside /boot/grub I have much less than 1Mb.
>
> Since the boot partition has 40Mb, why does my system say that is full
> if I only see less than 8Mb?
>
> ////////////////////
> tux grub # df -h | grep boot
> /dev/hdc1              40M   40M     0 100% /boot
> ////////////////////
>
> Thanks in advance.
>
> Richard.


and you are using which fs?

oh, and ls -lah might be more helpfull.
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]

On Thu, 21 Jun 2007 23:37:16 +0200, Hemmann, Volker Armin wrote:

> and you are using which fs?

I'd hazard a guess at reiserfs.
> 
> oh, and ls -lah might be more helpfull.

Along with df -T /boot


-- 
Neil Bothwick

Windows Error #09: Mouse not found. Press mouse button to continue.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] /boot without space.

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

On Thursday 21 June 2007 16:11:42 Ricardo Bevilacqua wrote:
> I was installing a boot splash when i got this message
>
> //////////////////////
> o Creating initramfs image..
> mv: writing «/boot/fbsplash-livecd-2007.0-1024x768»: There is no space
> left on the device.
> //////////////////////
>
> I was surprised so I checked the /boot partition

Try using:
du -xa /boot | sort -rn
as root to locate the space hogs, which may be hidden files.  (du does "lie" 
sometimes though, because the assumptions it makes about file size aren't 
always true.)

You might also fire up filelight and/or the file size view of konqueror 
(either would also need to be as root) if you prefer a graphical view.  (They 
will suffer from the same limitations as du, but their assumptions my be 
different.)

Oh, I'm not sure while filesystem you are using, but reiserfs reserves some 
space for the block usage bitmap and misc. metadata, and that takes up a 
number of MB.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] /boot without space.

[Ricardo Bevilacqua]

2007/6/21, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>:
> and you are using which fs?

I'm using reiserfs.

> oh, and ls -lah might be more helpfull.

tux boot # ls -lah
total 6,8M
drwxr-xr-x  5 root root  488 jun 21 17:56 .
drwxrwxrwx 20 root root  496 may 15 20:47 ..
lrwxrwxrwx  1 root root    1 may  2 20:26 boot -> .
lrwxrwxrwx  1 root root   23 may 14 16:24 config -> config-2.6.20-gentoo-r7
-rw-r--r--  1 root root  42K may 14 16:24 config-2.6.20-gentoo-r7
-rw-------  1 root root 8,0K jun 21 17:56 fbsplash-livecd-2007.0-1024x768
-rw-r--r--  1 root root 2,9M jun 21 16:44 gentoo-2.6.20
drwxr-xr-x  2 root root  632 jun 21 18:53 grub
-rw-r--r--  1 root root    0 ago  3  2006 .keep
lrwxrwxrwx  1 root root   27 may 14 16:24 System.map ->
System.map-2.6.20-gentoo-r7
-rw-r--r--  1 root root 989K may 14 16:24 System.map-2.6.20-gentoo-r7
lrwxrwxrwx  1 root root   24 may 14 16:24 vmlinuz -> vmlinuz-2.6.20-gentoo-r7
-rw-r--r--  1 root root  56K jun 21 16:44 vmlinuz-2.6.20-gentoo-r7
-rw-r--r--  1 root root 2,9M jun 21 16:06 vmlinuz-2.6.20-gentoo-r7.old

Thanks for the tip, this is a better output.

Let me know if there is any other information that I missed.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Ricardo Bevilacqua]

2007/6/21, Neil Bothwick <neil@digimed.co.uk>:
> On Thu, 21 Jun 2007 23:37:16 +0200, Hemmann, Volker Armin wrote:
> > oh, and ls -lah might be more helpfull.
>
> Along with df -T /boot

tux boot # df -T /boot
               Type       1K Blocks   Used    Available Use% Mounted in
/dev/hdc1 reiserfs       40120     40120         0       100%     /boot

That isn't the literal output, I had to translate it, the values are
the same anyway.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Hemmann, Volker Armin]

On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
> 2007/6/21, Neil Bothwick <neil@digimed.co.uk>:
> > On Thu, 21 Jun 2007 23:37:16 +0200, Hemmann, Volker Armin wrote:
> > > oh, and ls -lah might be more helpfull.
> >
> > Along with df -T /boot
>
> tux boot # df -T /boot
>                Type       1K Blocks   Used    Available Use% Mounted in
> /dev/hdc1 reiserfs       40120     40120         0       100%     /boot
>
> That isn't the literal output, I had to translate it, the values are
> the same anyway.

I would hazard the guess, that your boot is full because the journal uses 32mb 
for itself.

There is NO reason to use ANY journaling fs for /boot.

You can try two things: make journal smaller (I don't know how) or change boot 
to ext2 (good choice).

I really love reiserfs, but it is the wrong fs for /boot. like ext3 is the 
wrong fs for /boot. Or Xfs. or jfs.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Ricardo Bevilacqua]

2007/6/21, Boyd Stephen Smith Jr. <bss03@volumehost.net>:
> Try using:
> du -xa /boot | sort -rn
> as root to locate the space hogs, which may be hidden files.  (du does "lie"
> sometimes though, because the assumptions it makes about file size aren't
> always true.)

tux ric # du -xa /boot | sort -rn
7283    /boot
2935    /boot/gentoo-2.6.20
2903    /boot/vmlinuz-2.6.20-gentoo-r7.old
993     /boot/System.map-2.6.20-gentoo-r7
345     /boot/grub
100     /boot/grub/stage2_eltorito
100     /boot/grub/stage2
56      /boot/vmlinuz-2.6.20-gentoo-r7
44      /boot/config-2.6.20-gentoo-r7
36      /boot/grub/splash.xpm.gz
12      /boot/grub/xfs_stage1_5
12      /boot/grub/reiserfs_stage1_5
8       /boot/grub/vstafs_stage1_5
8       /boot/grub/ufs2_stage1_5
8       /boot/grub/minix_stage1_5
8       /boot/grub/jfs_stage1_5
8       /boot/grub/iso9660_stage1_5
8       /boot/grub/ffs_stage1_5
8       /boot/grub/fat_stage1_5
8       /boot/grub/e2fs_stage1_5
4       /boot/grub/stage1
4       /boot/grub/grub.conf.sample
4       /boot/grub/grub.conf
4       /boot/grub/device.map
4       /boot/grub/default
0       /boot/vmlinuz
0       /boot/System.map
0       /boot/.keep
0       /boot/grub/menu.lst
0       /boot/config
0       /boot/boot

Ok, this shows me every file on /boot, only ~15Mb, which is more that
I had calculated before.

> You might also fire up filelight and/or the file size view of konqueror
> (either would also need to be as root) if you prefer a graphical view.  (They
> will suffer from the same limitations as du, but their assumptions my be
> different.)

Almost the same with a graphical view.

> Oh, I'm not sure while filesystem you are using, but reiserfs reserves some
> space for the block usage bitmap and misc. metadata, and that takes up a
> number of MB.

You might be right, but still, we have found out that the files are
~15Mb, if the partition has a size of 40Mb, is it possible that
reiserfs is using almost 25Mb for storing data?
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Ricardo Bevilacqua]

2007/6/21, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>:
> I would hazard the guess, that your boot is full because the journal uses 32mb
> for itself.
>
> There is NO reason to use ANY journaling fs for /boot.
>
> You can try two things: make journal smaller (I don't know how) or change boot
> to ext2 (good choice).
>
> I really love reiserfs, but it is the wrong fs for /boot. like ext3 is the
> wrong fs for /boot. Or Xfs. or jfs.

I agree with you, actually, I can't figure out any good reason for
using journaling file system for /boot.

But, just in case, I'm going to investigate a little bit more.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Hemmann, Volker Armin]

On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
> 2007/6/21, Boyd Stephen Smith Jr. <bss03@volumehost.net>:
> > Try using:
> > du -xa /boot | sort -rn
> > as root to locate the space hogs, which may be hidden files.  (du does
> > "lie" sometimes though, because the assumptions it makes about file size
> > aren't always true.)
>
> tux ric # du -xa /boot | sort -rn
> 7283    /boot
> 2935    /boot/gentoo-2.6.20
> 2903    /boot/vmlinuz-2.6.20-gentoo-r7.old
> 993     /boot/System.map-2.6.20-gentoo-r7
> 345     /boot/grub
> 100     /boot/grub/stage2_eltorito
> 100     /boot/grub/stage2
> 56      /boot/vmlinuz-2.6.20-gentoo-r7
> 44      /boot/config-2.6.20-gentoo-r7
> 36      /boot/grub/splash.xpm.gz
> 12      /boot/grub/xfs_stage1_5
> 12      /boot/grub/reiserfs_stage1_5
> 8       /boot/grub/vstafs_stage1_5
> 8       /boot/grub/ufs2_stage1_5
> 8       /boot/grub/minix_stage1_5
> 8       /boot/grub/jfs_stage1_5
> 8       /boot/grub/iso9660_stage1_5
> 8       /boot/grub/ffs_stage1_5
> 8       /boot/grub/fat_stage1_5
> 8       /boot/grub/e2fs_stage1_5
> 4       /boot/grub/stage1
> 4       /boot/grub/grub.conf.sample
> 4       /boot/grub/grub.conf
> 4       /boot/grub/device.map
> 4       /boot/grub/default
> 0       /boot/vmlinuz
> 0       /boot/System.map
> 0       /boot/.keep
> 0       /boot/grub/menu.lst
> 0       /boot/config
> 0       /boot/boot
>
> Ok, this shows me every file on /boot, only ~15Mb, which is more that
> I had calculated before.
>
> > You might also fire up filelight and/or the file size view of konqueror
> > (either would also need to be as root) if you prefer a graphical view. 
> > (They will suffer from the same limitations as du, but their assumptions
> > my be different.)
>
> Almost the same with a graphical view.
>
> > Oh, I'm not sure while filesystem you are using, but reiserfs reserves
> > some space for the block usage bitmap and misc. metadata, and that takes
> > up a number of MB.
>
> You might be right, but still, we have found out that the files are
> ~15Mb, if the partition has a size of 40Mb, is it possible that
> reiserfs is using almost 25Mb for storing data?

it is using per default 32mb for its journal.

The missing mb (32+15>40) comes from two facts:
du lies
and tail packing.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Albert Hopkins]

On Fri, 2007-06-22 at 00:41 +0200, Hemmann, Volker Armin wrote:
> it is using per default 32mb for its journal.
> 
> The missing mb (32+15>40) comes from two facts:
> du lies
> and tail packing. 

Actually I think he misread the output of du.  It should be ~7283
for /boot at the "root" level.  Don't add the individual
subdirectories/files coz you're just counting everything twice.  Add
8193*4096 bytes for the reiserfs journal and you've got 40055 (~40G).
--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Hemmann, Volker Armin]

On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
> 2007/6/21, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>:
> > I would hazard the guess, that your boot is full because the journal uses
> > 32mb for itself.
> >
> > There is NO reason to use ANY journaling fs for /boot.
> >
> > You can try two things: make journal smaller (I don't know how) or change
> > boot to ext2 (good choice).
> >
> > I really love reiserfs, but it is the wrong fs for /boot. like ext3 is
> > the wrong fs for /boot. Or Xfs. or jfs.
>
> I agree with you, actually, I can't figure out any good reason for
> using journaling file system for /boot.
>
> But, just in case, I'm going to investigate a little bit more.

I don't think that you need to investigate more. Just be carefull when nuking 
the fs - you have to setup grub after that again. It might be smart to save 
the configs in /boot/grub ;)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Ricardo Bevilacqua]

2007/6/21, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>:
> I don't think that you need to investigate more. Just be carefull when nuking
> the fs - you have to setup grub after that again. It might be smart to save
> the configs in /boot/grub ;)

Any advice before doing that? =)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Hemmann, Volker Armin]

On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
> 2007/6/21, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>:
> > I don't think that you need to investigate more. Just be carefull when
> > nuking the fs - you have to setup grub after that again. It might be
> > smart to save the configs in /boot/grub ;)
>
> Any advice before doing that? =)

reread the grub setup instructions on gentoo.org?
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: /boot without space.

[Alexander Skwar]

Ricardo Bevilacqua <rus.spes@gmail.com> wrote:

> Here I just have ~7Mb.
> Inside /boot/grub I have much less than 1Mb.
> 
> Since the boot partition has 40Mb, why does my system say that is full
> if I only see less than 8Mb?
> 
> ////////////////////
> tux grub # df -h | grep boot
> /dev/hdc1              40M   40M     0 100% /boot
> ////////////////////

Don't use ext3 for /boot - there's just no need for a journal on
/boot, as you'll VERY rarely write to it. For boot, the journal
is just a waste - a waste of 32m, to be exact. Combined with
your ~7Mb, this gives 40m.

Cheers,

Alexander Skwar

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: /boot without space.

[Alexander Skwar]

Alexander Skwar <listen@alexander.skwar.name> wrote:

> Don't use ext3 for /boot - there's just no need for a journal on
> /boot, as you'll VERY rarely write to it. For boot, the journal
> is just a waste - a waste of 32m, to be exact. Combined with
> your ~7Mb, this gives 40m.

I was wrong. ext3 does not use 32m for journal on such a small
filesystem.

Alexander Skwar

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Mick]

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On Friday 22 June 2007 02:38, Hemmann, Volker Armin wrote:
> On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
> > 2007/6/21, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>:
> > > I don't think that you need to investigate more. Just be carefull when
> > > nuking the fs - you have to setup grub after that again. It might be
> > > smart to save the configs in /boot/grub ;)
> >
> > Any advice before doing that? =)
>
> reread the grub setup instructions on gentoo.org?

Make a back up:

# mount /boot
# cd /boot
# tar cpvf /tmp/boot_backup.tar . 

Then mkfs <type> on your /boot partition, re-install grub and untar the /boot 
archive and cp -a <kernel_files, grub.conf, etc.> from /tmp to /boot as 
needed.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] /boot without space.

[Benno Schulenberg]

> tux boot # df -T /boot
>                Type       1K Blocks   Used    Available Use%
> Mounted in /dev/hdc1 reiserfs       40120     40120         0    
>   100%     /boot
>
> That isn't the literal output, I had to translate it,

There's no need to translate it.  When posting output of a command, 
preceding the command with LC_ALL=C will undo any localisation.  In 
this case: 'LC_ALL=C  df -T /boot' should produce unlocalised text.  

Benno
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /boot without space.

[Ricardo Bevilacqua]

Well, finally, the trouble was the file system.
Now I have changed it from reiserfs to ext2. No troubles at all, as you said.

Thanks for helping me with this newbie mistake =)
-- 
gentoo-user@gentoo.org mailing list