[gentoo-laptop] emerge broken after update gcc

[gentoo-laptop] emerge broken after update gcc

[maillists]

Hi,

I just updated gcc and am running 4.1.1. but now my emerge does not work
at all.

Here is an example of trying to update portage for example:

thor rbragg # emerge -a portage
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'

These are the packages that would be merged, in order:

Calculating dependencies  -
... done!
[ebuild   R   ] sys-apps/portage-2.1.1-r2

Would you like to merge these packages? [Yes/No] Traceback (most recent
call last):
  File "/usr/bin/emerge", line 4049, in ?
    emerge_main()
  File "/usr/bin/emerge", line 4044, in emerge_main
    myopts, myaction, myfiles, spinner)
  File "/usr/bin/emerge", line 3584, in action_build
    mergetask.merge(pkglist, favorites, mtimedb)
  File "/usr/bin/emerge", line 1854, in merge
    "\n".join(myfavdict.values()))
  File "/usr/lib/portage/pym/portage_util.py", line 738, in write_atomic
    raise ReadOnlyFileSystem(func_call)
portage_exception.ReadOnlyFileSystem:
"write_atomic('/var/lib/portage/world')"
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'



The "/var/log/emerge.log" file is owned by portage.portage, and mode is
ug+rw. and the "/var/lib/portage/world" file is owned by root.root with
u+rw and go+r I am running my emerge as root. It seems that I can't even
chown the would file.

I tried this to:
thor rbragg # chown root.portage /var/lib/portage/world
chown: changing ownership of `/var/lib/portage/world': Read-only file
system

Does anybody know what happened?

This is on a powerbook (500Mhz g3 pismo)

Thanks
rick


-- 
gentoo-laptop@gentoo.org mailing list

Re: [gentoo-laptop] emerge broken after update gcc

[Jürgen Pierau]

maillists schrieb:
> Hi,
>
> I just updated gcc and am running 4.1.1. but now my emerge does not work
> at all.
>
> Here is an example of trying to update portage for example:
>
> thor rbragg # emerge -a portage
> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
>   
It looks like your filesystem is mounted with the 'ro' option. Seeing 
the output of 'mount' would help.

Bye,
Jürgen
-- 
gentoo-laptop@gentoo.org mailing list

Re: [gentoo-laptop] emerge broken after update gcc

[maillists]

On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote:
> maillists schrieb:
> > Hi,
> >
> > I just updated gcc and am running 4.1.1. but now my emerge does not work
> > at all.
> >
> > Here is an example of trying to update portage for example:
> >
> > thor rbragg # emerge -a portage
> > emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> >   
> It looks like your filesystem is mounted with the 'ro' option. Seeing 
> the output of 'mount' would help.
> 
> Bye,
> Jürgen

Hi,

Thanks, here is the "mount" command: As you can see I also have NFS
mount some local file shares from another host. My system is
on /dev/hda4. What is the "commit=0" thing?

thor rbragg # mount
/dev/hda4 on / type ext3 (rw,commit=0)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
none on /proc/bus/usb type usbfs (rw)
host.home.net:/home/share/accounts on /home/rbragg/accounts type nfs
(rw,rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.0.11,addr=192.168.0.11)
host.home.net:/home/share/artwork on /home/rbragg/artwork type nfs
(rw,rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.0.11,addr=192.168.0.11)
host.home.net:/home/share/clients on /home/rbragg/clients type nfs
(rw,rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.0.11,addr=192.168.0.11)
host.home.net:/home/share/gmnet on /home/rbragg/gmnet type nfs
(rw,rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.0.11,addr=192.168.0.11)
host.home.net:/home/share/mp3 on /home/rbragg/mp3 type nfs
(rw,rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.0.11,addr=192.168.0.11)

Thanks
rick


-- 
gentoo-laptop@gentoo.org mailing list

RE: [gentoo-laptop] emerge broken after update gcc

[Nelson, David (ED, PAR&D)]

> -----Original Message-----
> From: maillists [mailto:lists@gmnet.net]
> Sent: 04 January 2007 13:44
> To: gentoo-laptop@lists.gentoo.org
> Subject: Re: [gentoo-laptop] emerge broken after update gcc
>
> Thanks, here is the "mount" command: As you can see I also have NFS
> mount some local file shares from another host. My system is
> on /dev/hda4. What is the "commit=0" thing?

I love Google ;)

http://www.die.net/doc/linux/man/man8/mount.8.html

"commit=nrsec
    Sync all data and metadata every nrsec seconds. The default value is 5 seconds. Zero means default."

David

Note: These views are my own, advice is provided with no guarantee of success. I do not represent anyone else in any emails I send to this list.

-- 
gentoo-laptop@gentoo.org mailing list

Re: [gentoo-laptop] emerge broken after update gcc

[Jürgen Pierau]

maillists schrieb:
> On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote:
>   
>> maillists schrieb:
>>     
>>> Hi,
>>>
>>> I just updated gcc and am running 4.1.1. but now my emerge does not work
>>> at all.
>>>
>>> Here is an example of trying to update portage for example:
>>>
>>> thor rbragg # emerge -a portage
>>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
>>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
>>>   
>>>       
>> It looks like your filesystem is mounted with the 'ro' option. Seeing 
>> the output of 'mount' would help.
>>
>>     
> Thanks, here is the "mount" command: As you can see I also have NFS
> mount some local file shares from another host. My system is
> on /dev/hda4. What is the "commit=0" thing?
>
> thor rbragg # mount
> /dev/hda4 on / type ext3 (rw,commit=0)
>   
Hi Rick,

the mount line for your / looks ok to me (don't know about the commit, 
but afaik it shouldn't cause trouble). I'm somewhat at a loss. 
"Read-only file system" suggests that the file system driver (ext3 in 
this case) refuses to write to /dev/hda4. This should be reflected by a 
'ro' (for read-only) in the mount line. Instead, there is 'rw' which is 
quite what it should be. It just doesn't fit the error message.

I guess you have made sure that /var/log exists. Type 'dmesg' and check 
the output for messages concerning hda4 or ext3/ext2. Maybe the fs 
driver has decided to (take a) break for some reason (like fs errors, 
read errors or some such fancy occurrence).

C'Ya,
Jürgen



-- 
gentoo-laptop@gentoo.org mailing list

Re: [gentoo-laptop] emerge broken after update gcc

[Boyd Stephen Smith Jr.]

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

On Thursday 04 January 2007 07:43, maillists <lists@gmnet.net> wrote 
about 'Re: [gentoo-laptop] emerge broken after update gcc':
> On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote:
> > maillists schrieb:
> > > I just updated gcc and am running 4.1.1. but now my emerge does not
> > > work at all.
> > >
> > > Here is an example of trying to update portage for example:
> > >
> > > thor rbragg # emerge -a portage
> > > emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > > emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > It looks like your filesystem is mounted with the 'ro' option. Seeing
> > the output of 'mount' would help.
> Thanks, here is the "mount" command:
> /dev/hda4 on / type ext3 (rw,commit=0)

Try:
mount -o remount,rw /
as root.

If that does not fix the problem,
cat /proc/mounts
and let me know the result.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-laptop] emerge broken after update gcc

[maillists]

On Thu, 2007-01-04 at 15:53 +0100, Jürgen Pierau wrote:
> maillists schrieb:
> > On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote:
> >   
> >> maillists schrieb:
> >>     
> >>> Hi,
> >>>
> >>> I just updated gcc and am running 4.1.1. but now my emerge does not work
> >>> at all.
> >>>
> >>> Here is an example of trying to update portage for example:
> >>>
> >>> thor rbragg # emerge -a portage
> >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> >>>   
> >>>       
> >> It looks like your filesystem is mounted with the 'ro' option. Seeing 
> >> the output of 'mount' would help.
> >>
> >>     
> > Thanks, here is the "mount" command: As you can see I also have NFS
> > mount some local file shares from another host. My system is
> > on /dev/hda4. What is the "commit=0" thing?
> >
> > thor rbragg # mount
> > /dev/hda4 on / type ext3 (rw,commit=0)
> >   
> Hi Rick,
> 
> the mount line for your / looks ok to me (don't know about the commit, 
> but afaik it shouldn't cause trouble). I'm somewhat at a loss. 
> "Read-only file system" suggests that the file system driver (ext3 in 
> this case) refuses to write to /dev/hda4. This should be reflected by a 
> 'ro' (for read-only) in the mount line. Instead, there is 'rw' which is 
> quite what it should be. It just doesn't fit the error message.
> 
> I guess you have made sure that /var/log exists. Type 'dmesg' and check 
> the output for messages concerning hda4 or ext3/ext2. Maybe the fs 
> driver has decided to (take a) break for some reason (like fs errors, 
> read errors or some such fancy occurrence).
> 
> C'Ya,
> Jürgen
> 

Thanks,

I decided to reboot (even though I unmerged pam-login) I was forced to
run fsck manually during boot and had alot of "orphaned inodes and tons
of other errors on the disk.  Now it fails to start /etc/init.d/clock
and dies. Can't even boot!

This whole thing started in the middle of updating glibc, and that never
finished. I was trying to update "emerge -auvDN system" and about 1/2
hour into that, I got the first Read Only error... 

I'm hosed with the whole thing. Does anyone know when gentoo 2007.1 will
be released?

thanks again for all the help!
rick

> 


-- 
gentoo-laptop@gentoo.org mailing list

Re: [gentoo-laptop] emerge broken after update gcc

[Devon Miller]

On 1/4/07, maillists <lists@gmnet.net> wrote:
> On Thu, 2007-01-04 at 15:53 +0100, Jürgen Pierau wrote:
> > maillists schrieb:
> > > On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote:
> > >
> > >> maillists schrieb:
> > >>
> > >>> Hi,
> > >>>
> > >>> I just updated gcc and am running 4.1.1. but now my emerge does not work
> > >>> at all.
> > >>>
> > >>> Here is an example of trying to update portage for example:
> > >>>
> > >>> thor rbragg # emerge -a portage
> > >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > >>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> > >>>
> > >>>
> > >> It looks like your filesystem is mounted with the 'ro' option. Seeing
> > >> the output of 'mount' would help.
> > >>
> > >>
> > > Thanks, here is the "mount" command: As you can see I also have NFS
> > > mount some local file shares from another host. My system is
> > > on /dev/hda4. What is the "commit=0" thing?
> > >
> > > thor rbragg # mount
> > > /dev/hda4 on / type ext3 (rw,commit=0)
> > >
> > Hi Rick,
> >
> > the mount line for your / looks ok to me (don't know about the commit,
> > but afaik it shouldn't cause trouble). I'm somewhat at a loss.
> > "Read-only file system" suggests that the file system driver (ext3 in
> > this case) refuses to write to /dev/hda4. This should be reflected by a
> > 'ro' (for read-only) in the mount line. Instead, there is 'rw' which is
> > quite what it should be. It just doesn't fit the error message.
> >
> > I guess you have made sure that /var/log exists. Type 'dmesg' and check
> > the output for messages concerning hda4 or ext3/ext2. Maybe the fs
> > driver has decided to (take a) break for some reason (like fs errors,
> > read errors or some such fancy occurrence).
> >
> > C'Ya,
> > Jürgen
> >
>
> Thanks,
>
> I decided to reboot (even though I unmerged pam-login) I was forced to
> run fsck manually during boot and had alot of "orphaned inodes and tons
> of other errors on the disk.  Now it fails to start /etc/init.d/clock
> and dies. Can't even boot!
>
> This whole thing started in the middle of updating glibc, and that never
> finished. I was trying to update "emerge -auvDN system" and about 1/2
> hour into that, I got the first Read Only error...
>
> I'm hosed with the whole thing. Does anyone know when gentoo 2007.1 will
> be released?
>
> thanks again for all the help!
> rick

If you haven't started reiinstalling yet, try this (I know I've done
this on other distros, but to be honest, I haven't tried it with
Gentoo):
    assuming you're using grub
    select your boot image and press 'e'  for edit
    select the kernel line and, again,  press 'e'  for edit
    move to the end of the line and append: init=/bin/bash
    press return
    press 'b' for boot

If all goes well, it should drop you directly into a bash command prompt.
The root is probably mounted ro, so make it writable with mount -oremount,rw /
>From there you should be able to use rc-update to remove clock from
the boot run-level.
Remount root as ro before exiting the shell (mount -o remount,ro /)

dcm

-- 
gentoo-laptop@gentoo.org mailing list

Re: [gentoo-laptop] emerge broken after update gcc

[Randy Barlow]

On Thu, 2007-01-04 at 10:26 -0500, maillists wrote:
> I decided to reboot (even though I unmerged pam-login) I was forced to
> run fsck manually during boot and had alot of "orphaned inodes and tons
> of other errors on the disk.  Now it fails to start /etc/init.d/clock
> and dies. Can't even boot!

Perhaps your drive is dead?

Randy Barlow
http://www.electronsweatshop.com
... faster BogoMIPS calculations (yes, it now boots 2 seconds faster
than it used to: we're considering changing the name from "Linux" to
"InstaBOOT" -- Linus, in the announcement for 1.3.26

-- 
gentoo-laptop@gentoo.org mailing list