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 [EMAIL PROTECTED]:
I don't think that you need to investigate more. Just be carefull when
nuking the fs - you have to setup grub after that
tux boot # df -T /boot
Type 1K Blocks UsedAvailable 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,
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 =)
--
[EMAIL PROTECTED] mailing list
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
/
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
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.
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
2007/6/21, Hemmann, Volker Armin [EMAIL PROTECTED]:
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 root1
2007/6/21, Neil Bothwick [EMAIL PROTECTED]:
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 UsedAvailable Use% Mounted in
/dev/hdc1 reiserfs
On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
2007/6/21, Neil Bothwick [EMAIL PROTECTED]:
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
2007/6/21, Boyd Stephen Smith Jr. [EMAIL PROTECTED]:
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
2007/6/21, Hemmann, Volker Armin [EMAIL PROTECTED]:
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
On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
2007/6/21, Boyd Stephen Smith Jr. [EMAIL PROTECTED]:
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
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+1540) 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
On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
2007/6/21, Hemmann, Volker Armin [EMAIL PROTECTED]:
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
2007/6/21, Hemmann, Volker Armin [EMAIL PROTECTED]:
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? =)
--
[EMAIL PROTECTED]
On Freitag, 22. Juni 2007, Ricardo Bevilacqua wrote:
2007/6/21, Hemmann, Volker Armin [EMAIL PROTECTED]:
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 ;)
17 matches
Mail list logo
