[lug] Read-only filesystem

[Hugh Brown]

On Wed, 3 Jan 2007, Gary Hodges wrote:

> Jeff Schroeder wrote:
> > Gary wrote:
> >
> >> When copying data to one of the disks I
> >> will eventually get an error that says in part "cannot create regular
> >> file" "read-only file system."
> >
> > If there's a hardware failure in the hard drive, the kernel will
> > sometimes instruct 'mount' to change the filesystem to read-only in
> > order to prevent additional damage.  This might be what's happening;
> > check your kernel logs or even 'dmesg' to see if you're getting reports
> > of bad sectors or something along those lines.
>
> Thanks for the reply.  I see these messages with dmesg:
>
> [ 2890.878069] sd 6:0:2:0: SCSI error: return code = 0x8000002
> [ 2890.878073] sdc: Current: sense key: Aborted Command
> [ 2890.878075]     Additional sense: Scsi parity error
> [ 2890.878081] end_request: I/O error, dev sdc, sector 156253039
> [ 2891.291088] REISERFS: abort (device sdc1): Journal write error in
> flush_commit_list
> [ 2891.291094] REISERFS: Aborting journal for filesystem on sdc1
>

Yep, you've got a bad drive or a bad controller.  Get the data off the
disk if possible.

Hugh