| 1 |
maillists schrieb: |
| 2 |
> On Thu, 2007-01-04 at 12:32 +0100, Jürgen Pierau wrote: |
| 3 |
> |
| 4 |
>> maillists schrieb: |
| 5 |
>> |
| 6 |
>>> Hi, |
| 7 |
>>> |
| 8 |
>>> I just updated gcc and am running 4.1.1. but now my emerge does not work |
| 9 |
>>> at all. |
| 10 |
>>> |
| 11 |
>>> Here is an example of trying to update portage for example: |
| 12 |
>>> |
| 13 |
>>> thor rbragg # emerge -a portage |
| 14 |
>>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log' |
| 15 |
>>> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log' |
| 16 |
>>> |
| 17 |
>>> |
| 18 |
>> It looks like your filesystem is mounted with the 'ro' option. Seeing |
| 19 |
>> the output of 'mount' would help. |
| 20 |
>> |
| 21 |
>> |
| 22 |
> Thanks, here is the "mount" command: As you can see I also have NFS |
| 23 |
> mount some local file shares from another host. My system is |
| 24 |
> on /dev/hda4. What is the "commit=0" thing? |
| 25 |
> |
| 26 |
> thor rbragg # mount |
| 27 |
> /dev/hda4 on / type ext3 (rw,commit=0) |
| 28 |
> |
| 29 |
Hi Rick, |
| 30 |
|
| 31 |
the mount line for your / looks ok to me (don't know about the commit, |
| 32 |
but afaik it shouldn't cause trouble). I'm somewhat at a loss. |
| 33 |
"Read-only file system" suggests that the file system driver (ext3 in |
| 34 |
this case) refuses to write to /dev/hda4. This should be reflected by a |
| 35 |
'ro' (for read-only) in the mount line. Instead, there is 'rw' which is |
| 36 |
quite what it should be. It just doesn't fit the error message. |
| 37 |
|
| 38 |
I guess you have made sure that /var/log exists. Type 'dmesg' and check |
| 39 |
the output for messages concerning hda4 or ext3/ext2. Maybe the fs |
| 40 |
driver has decided to (take a) break for some reason (like fs errors, |
| 41 |
read errors or some such fancy occurrence). |
| 42 |
|
| 43 |
C'Ya, |
| 44 |
Jürgen |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
-- |
| 49 |
gentoo-laptop@g.o mailing list |
Archives