Thanks for the help. More below....
On Mon, 1 Nov 2004, Richard Darst wrote:
> I once had something like this happening to me. Check the output from
> "dmesg" and see if there are any clues.
oh yeah. lookie here...
[EMAIL PROTECTED]:~$ dmesg | head
0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
...and it continues this way, on and on, identically except for a hiccup
in the last two lines, see for yourself...
[EMAIL PROTECTED]:~$ dmesg | tail
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,1)) in start_transaction: Journal has aborted
ext3_abort called.
EXT3-fs abort (device ide0(3,1)): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs abort (device ide0(3,1)): ext3_remount: Abort forced by user
...now, it does this for 212 lines!!! see...
[EMAIL PROTECTED]:~$ dmesg | wc -l
212
...does this clarify?
> maybe
> /var/log/{syslog,kern.log}.
There is all sortsa stuff in syslog....
homebase:/home/billj# head /var/log/syslog
Oct 26 06:26:23 localhost syslogd 1.4.1#15: restart.
Oct 26 06:50:56 localhost -- MARK --
Oct 26 07:10:56 localhost -- MARK --
Oct 26 07:17:01 localhost /USR/SBIN/CRON[1295]: (root) CMD ( run-parts
--report /etc/cron.hourly)
Oct 26 07:30:56 localhost -- MARK --
Oct 26 07:50:56 localhost -- MARK --
Oct 26 08:10:56 localhost -- MARK --
Oct 26 08:17:01 localhost /USR/SBIN/CRON[1297]: (root) CMD ( run-parts
--report /etc/cron.hourly)
Oct 26 08:30:56 localhost -- MARK --
Oct 26 08:50:56 localhost -- MARK --
...but it is all greek to me. 501 lines of greek...
homebase:/home/billj# wc -l /var/log/syslog
501 /var/log/syslog
...ditto for kern.log...
homebase:/home/billj# head /var/log/kern.log
Oct 24 20:11:54 localhost kernel: eth0: link down
Oct 24 20:11:56 localhost kernel: eth0: link up, 100Mbps, full-duplex, lpa
0x41E1
Oct 24 20:11:58 localhost kernel: eth0: link down
Oct 24 20:12:06 localhost kernel: eth0: link up, 100Mbps, full-duplex, lpa
0x41E1
Oct 24 20:12:24 localhost kernel: eth0: link down
Oct 24 20:16:25 localhost kernel: eth0: link up, 10Mbps, half-duplex, lpa
0x0000
Oct 24 20:16:25 localhost kernel: eth0: link down
Oct 24 20:24:25 localhost kernel: eth0: link down
Oct 24 20:30:43 localhost kernel: eth0: link down
Oct 24 20:32:50 localhost kernel: Kernel logging (proc) stopped.
...plus, there is lots of greek in kern.log too...
homebase:/home/billj# wc -l /var/log/kern.log
473 /var/log/kern.log
...hrm, i remember having connectivity issues and used ifup -a and
ifdown -a to try to fix it....maybe that is what "eth0: link down"
is about...but what is this stuff, snarfed from somewhere in the
middle...
Oct 24 20:50:57 localhost kernel: TCP: Hash tables configured (established
4096
bind 8192)
Oct 24 20:50:57 localhost kernel: Linux IP multicast router 0.06 plus
PIM-SM
Oct 24 20:50:57 localhost kernel: RAMDISK: cramfs filesystem found at
block 0
Oct 24 20:50:57 localhost kernel: RAMDISK: Loading 3808 blocks [1 disk]
into ram
disk...
|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^
H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-
^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H
/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^
H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-
^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H
/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^
H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-
^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H/^H-^H\^H|^H
/^Hdone.
Oct 24 20:50:57 localhost kernel: Freeing initrd memory: 3808k freed
...so, i am shooting in the dark. maybe i should email the entirety
of syslog and kern.log?
>
> You imply that it was working alright before, so I will assume that
> it's not configuration. For me, the disk had errors, so the kernel
yes, my computer was working fine since the install fest.
> was detecting errors and remounting the filesystem read-only as a
> safety catch.
>
> The way I bought myself more time without rebooting was:
>
> mount -o remount,rw /
homebase:/var/log# mount -o remount,rw /
mount: block device /dev/hda1 is write-protected, mounting read-only
...hrm...did not seem to have helped. let me check to see if
it did...
homebase:/var/log# exit
[EMAIL PROTECTED]:/var/log$ cd
[EMAIL PROTECTED]:~$ pwd
/home/billj
[EMAIL PROTECTED]:~$ echo testing45566 > junk.text
-bash: junk.text: Read-only file system
[EMAIL PROTECTED]:~$
...nope, still having the same sorta problem.
>
> This takes the filesystem that is ro (here, /) and moves it back to
> rw. Of course, the kernel made it ro for a reason, so beware. It may
> go back to ro if it detects more errors. If it doesn't fault again
> too fast, maybe you are OK for the time being. For me, I had to put a
> command in crontab to test for read-onlyness and remount if it was.
> (Not that it was the safest thing to do, but oh well).
>
> AFAIK, the mount command above is safe from the kernel point of view,
> but if the disk is bad or something is corrupted, there may be big
> problems. (i.e. I have no worries using it on a properly working
> system.) It won't let you switch from rw to ro if files are in use.
ah. well, i'm still ssh'ing and typing this email after i did the umount.
phew!
>
> Of course, maybe something entirely different is wrong. Tell us how
> it turns out.
okay. done.
hrm, i wonder, maybe i should just reboot? i am afraid it might not come
up again.
bill
>
> RD
>
>
> On Mon, Nov 01, 2004 at 03:56:57PM -0600, William L. Jarrold wrote:
> > Hi,
> >
> > I have been getting some odd behavior from my home debian linux
> > machine lately. Consider the following...
> >
> > [EMAIL PROTECTED]:~$ echo testing1234 >> junk.text
> > -bash: junk.text: Read-only file system
> > [EMAIL PROTECTED]:~$ ll junk.text
> > -rw-r--r-- 1 billj 79438 Oct 24 21:50 junk.text
> >
> > ...the above I consider very odd behavior. Just for grins, what
> > happens when I try this...
> >
> > [EMAIL PROTECTED]:~$ chmod u+w junk.text
> > chmod: changing permissions of `junk.text': Read-only file system
> > [EMAIL PROTECTED]:~$
> >
> > ...Hrm....Well, I searched google groups and am pretty bamboozled
> > (because fixes appear to involve scary commands such as "fsck" and
> > "mount" about which I know nearly nothing). They chatter in google
> > groups seems to further suggest hard drive issues. Uh oh.
> >
> > This seems to be the root of other new problems: E.g. Firefox is
> > complaining. And gunziping some archived files is impossible. When I
> > try these things, I get the same error, i.e. "Read-only file system".
> > I get a nice close shave with Occum's Razor so am I remiss in assuming
> > this is all caused by the same problem?
> >
> > Might these odd behaviors be related to sudden downtime freeze ups I
> > have had recently? Here is what happened: My linux box froze (and,
> > Dear Windows fans, this is something that happens about 1 time per
> > decade with me). I power cycled and it appeared to rebooted happily
> > (to my ignorant eyes at least). Did I try to write anything
> > immediately after this reboot? I dunno.
> >
> > I should also add that over the summer I had some signs of disk
> > failure in the making. In fact I emailed siglinux about them. This
> > was when I was budget cutting and my apt was warmer than usual.
> > People (off this list) said disks are very sensitive to temp. When I
> > lowered my room temp, failure ceased. So, I assumed all was well
> > enough.
> >
> > I've been getting that scary sound again (kind of like a relay that
> > keeps turning on an off...sometimes once in isolation, sometimes 5-20
> > times in rapid succession) tho maybe not as often/intensely. Has my
> > apt temp been creeping up again? Maybe. In response I've reverted to
> > keeping my apt cooler still. Has that sound happened less often? I
> > think so.
> >
> > So, I am going to suspect that I need:
> >
> > (1) a new hard drive...it is about to fail permanently.
> >
> > (2) until (1) more frequent backups to CD Rom.
> >
> > (3) a fix so that my file system is no longer read only.
> >
> > I can take care of (1) and (2) but can someone offer guidance on (3)?
> >
> > chmod does not seem to fix things.
> >
> > Bill
> > _______________________________________________
> > Siglinux mailing list
> > [EMAIL PROTECTED]
> > http://machito.utacm.org/mailman/listinfo/siglinux
> >
>
> --
> Richard Darst - [EMAIL PROTECTED] - lefschetz: up 58 days, 17:14
>
> "Ye shall know the truth and -- the truth shall make you free"
> 0x91DEC237 - http://rkd.zgib.net/pgp/
>
_______________________________________________
Siglinux mailing list
[EMAIL PROTECTED]
http://machito.utacm.org/mailman/listinfo/siglinux
