LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 01-04-2011, 07:45 PM   #1
mike11
Member
 
Registered: Apr 2009
Posts: 222

Rep: Reputation: 17
rsync error: Read-only file system (30)


Hi all,

I regularly rsync directories to an external usb drive. Recently I've started getting errors which look:
blah blah:Read-only file system (30)

The external usb drive has two partitions (ext3 and fat32) and I rsync to the ext3 one. The rsync command is
rsync -ahi --delete /home/mike/some_dir /media/usb_drive

Searching online, people have reported this error with faulty usb cables but everything was working fine until recently so it seem unlikely a usb cable would suddenly wear off.

Any suggestions?

TIA,
Mike.
 
Old 01-04-2011, 08:54 PM   #2
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,978
Blog Entries: 11

Rep: Reputation: 879Reputation: 879Reputation: 879Reputation: 879Reputation: 879Reputation: 879Reputation: 879
Anything of interest in /var/log/messages ?
Or the output of dmesg?



Cheers,
Tink
 
Old 01-06-2011, 05:12 AM   #3
mike11
Member
 
Registered: Apr 2009
Posts: 222

Original Poster
Rep: Reputation: 17
Thanks Tinkster.

Here's the (presumably) relevant output from /var/log/messages:
Code:
Jan  6 10:40:59 pc1 kernel: [  316.476021] usb 2-2: new high speed USB device using ehci_hcd and address 4
Jan  6 10:40:59 pc1 kernel: [  316.608971] usb 2-2: New USB device found, idVendor=04bb, idProduct=0125
Jan  6 10:40:59 pc1 kernel: [  316.608974] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  6 10:40:59 pc1 kernel: [  316.608977] usb 2-2: Product: HDPN-U          
Jan  6 10:40:59 pc1 kernel: [  316.608979] usb 2-2: Manufacturer: I-O DATA
Jan  6 10:40:59 pc1 kernel: [  316.608980] usb 2-2: SerialNumber: 0000000000E51AEB
Jan  6 10:40:59 pc1 kernel: [  316.609057] usb 2-2: configuration #1 chosen from 1 choice
Jan  6 10:40:59 pc1 kernel: [  316.668888] Initializing USB Mass Storage driver...
Jan  6 10:40:59 pc1 kernel: [  316.669008] scsi4 : SCSI emulation for USB Mass Storage devices
Jan  6 10:40:59 pc1 kernel: [  316.669119] usbcore: registered new interface driver usb-storage
Jan  6 10:40:59 pc1 kernel: [  316.669122] USB Mass Storage support registered.
Jan  6 10:41:04 pc1 kernel: [  321.675622] scsi 4:0:0:0: Direct-Access     I-O DATA HDPN-U           9.60 PQ: 0 ANSI: 0
Jan  6 10:41:04 pc1 kernel: [  321.675931] sd 4:0:0:0: Attached scsi generic sg2 type 0
Jan  6 10:41:04 pc1 kernel: [  321.676483] sd 4:0:0:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
Jan  6 10:41:04 pc1 kernel: [  321.677233] sd 4:0:0:0: [sdb] Write Protect is off
Jan  6 10:41:04 pc1 kernel: [  321.678610]  sdb: sdb1 sdb2
Jan  6 10:41:04 pc1 kernel: [  321.697476] sd 4:0:0:0: [sdb] Attached SCSI disk
Jan  6 10:41:05 pc1 kernel: [  322.525514] kjournald starting.  Commit interval 5 seconds
Jan  6 10:41:05 pc1 kernel: [  322.525518] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan  6 10:41:05 pc1 kernel: [  322.526236] EXT3 FS on sdb2, internal journal
Jan  6 10:41:05 pc1 kernel: [  322.526240] EXT3-fs: mounted filesystem with ordered data mode.
Jan  6 18:41:32 pc1 kernel: [29149.084686] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  6 18:41:32 pc1 kernel: [29149.084690] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current] 
Jan  6 18:41:32 pc1 kernel: [29149.084695] Info fld=0x0
Jan  6 18:41:32 pc1 kernel: [29149.084696] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
Jan  6 20:04:00 pc1 kernel: [34097.930287] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  6 20:04:00 pc1 kernel: [34097.930292] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current] 
Jan  6 20:04:00 pc1 kernel: [34097.930296] Info fld=0x0
Jan  6 20:04:00 pc1 kernel: [34097.930297] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
Jan  6 20:04:00 pc1 kernel: [34097.930308] lost page write due to I/O error on sdb2
Jan  6 20:04:01 pc1 kernel: [34097.939171] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  6 20:04:01 pc1 kernel: [34097.939177] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current] 
Jan  6 20:04:01 pc1 kernel: [34097.939181] Info fld=0x0
Jan  6 20:04:01 pc1 kernel: [34097.939182] sd 4:0:0:0: [sdb] Add. Sense: Invalid command operation code
Jan  6 20:04:01 pc1 kernel: [34097.939191] ------------[ cut here ]------------
Jan  6 20:04:01 pc1 kernel: [34097.939197] WARNING: at /build/buildd-linux-2.6_2.6.30-8-i386-Tm0Lt9/linux-2.6-2.6.30/debian/build/source_i386_none/fs/buffer.c:1152 mark_buffer_dirty+0x20/0x7a()
Jan  6 20:04:01 pc1 kernel: [34097.939200] Hardware name: OptiPlex 780                 
Jan  6 20:04:01 pc1 kernel: [34097.939202] Modules linked in: nls_utf8 nls_cp437 usb_storage i915 drm i2c_algo_bit video output ppdev lp acpi_cpufreq cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_powersave binfmt_misc fuse vfat fat nls_base loop snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc i2c_i801 i2c_core dcdbas processor button parport_pc pcspkr parport psmouse evdev wmi serio_raw ext3 jbd mbcache sg sd_mod crc_t10dif sr_mod cdrom ide_pci_generic usbhid hid ide_core uhci_hcd ata_piix ata_generic libata scsi_mod e1000e ehci_hcd usbcore intel_agp agpgart thermal fan thermal_sys [last unloaded: scsi_wait_scan]
Jan  6 20:04:01 pc1 kernel: [34097.939259] Pid: 2598, comm: kjournald Not tainted 2.6.30-2-686 #1
Jan  6 20:04:01 pc1 kernel: [34097.939262] Call Trace:
Jan  6 20:04:01 pc1 kernel: [34097.939267]  [<c0127150>] ? warn_slowpath_common+0x5e/0x8a
Jan  6 20:04:01 pc1 kernel: [34097.939270]  [<c0127186>] ? warn_slowpath_null+0xa/0xc
Jan  6 20:04:01 pc1 kernel: [34097.939273]  [<c01a683e>] ? mark_buffer_dirty+0x20/0x7a
Jan  6 20:04:01 pc1 kernel: [34097.939284]  [<f864129c>] ? journal_update_superblock+0x5b/0x99 [jbd]
Jan  6 20:04:01 pc1 kernel: [34097.939293]  [<f86413e3>] ? __journal_abort_soft+0x7d/0x83 [jbd]
Jan  6 20:04:01 pc1 kernel: [34097.939297]  [<c0204805>] ? snprintf+0x16/0x18
Jan  6 20:04:01 pc1 kernel: [34097.939301]  [<c031cd5d>] ? printk+0xe/0x11
Jan  6 20:04:01 pc1 kernel: [34097.939309]  [<f8641d76>] ? journal_bmap+0x4f/0x64 [jbd]
Jan  6 20:04:01 pc1 kernel: [34097.939318]  [<f863f087>] ? journal_commit_transaction+0x700/0xd55 [jbd]
Jan  6 20:04:01 pc1 kernel: [34097.939323]  [<c012e6af>] ? lock_timer_base+0x19/0x35
Jan  6 20:04:01 pc1 kernel: [34097.939331]  [<f8641a63>] ? kjournald+0xb7/0x1d2 [jbd]
Jan  6 20:04:01 pc1 kernel: [34097.939335]  [<c0136bce>] ? autoremove_wake_function+0x0/0x2d
Jan  6 20:04:01 pc1 kernel: [34097.939343]  [<f86419ac>] ? kjournald+0x0/0x1d2 [jbd]
Jan  6 20:04:01 pc1 kernel: [34097.939346]  [<c01368dc>] ? kthread+0x42/0x67
Jan  6 20:04:01 pc1 kernel: [34097.939349]  [<c013689a>] ? kthread+0x0/0x67
Jan  6 20:04:01 pc1 kernel: [34097.939352]  [<c0103a97>] ? kernel_thread_helper+0x7/0x10
Jan  6 20:04:01 pc1 kernel: [34097.939355] ---[ end trace 9fd1cebbb6055d75 ]---
Jan  6 20:04:02 pc1 kernel: [34099.858666] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858672] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858676] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858681] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858687] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858691] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858695] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858698] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858731] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858735] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858749] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858768] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858771] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858786] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858804] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858814] __journal_remove_journal_head: freeing b_committed_data
Jan  6 20:04:02 pc1 kernel: [34099.858820] __journal_remove_journal_head: freeing b_committed_data
these seem suspicious:
Code:
Jan  6 10:41:05 pc1 kernel: [  322.525518] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan  6 10:41:05 pc1 kernel: [  322.526236] EXT3 FS on sdb2, internal journal
Jan  6 10:41:05 pc1 kernel: [  322.526240] EXT3-fs: mounted filesystem with ordered data mode.
Jan  6 18:41:32 pc1 kernel: [29149.084686] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  6 18:41:32 pc1 kernel: [29149.084690] sd 4:0:0:0: [sdb] Sense Key : Illegal Request [current]
The funny thing is that if I manually umount and then mount the usb drive everything works fine. It seems like it get automatically umounted after some time and I have to manually re-mount it.

Thanks,
Mike.
 
Old 01-06-2011, 09:59 AM   #4
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,978
Blog Entries: 11

Rep: Reputation: 879Reputation: 879Reputation: 879Reputation: 879Reputation: 879Reputation: 879Reputation: 879
The messages to me suggest either
a) a faulty piece of hardware
or
b) a low-level driver at fault
or
c) a USB disconnect caused by the HDD itself ...

I had similar issues w/ my external Seagate 1TB device
until I added
Code:
SUBSYSTEMS=="scsi",DRIVERS=="sd",ATTRS{vendor}=="Seagate*",ATTRS{model}=="Desktop*",RUN+="/bin/sh -c echo 1 > /sys/class/scsi_disk/%k/allow_restart'"
SUBSYSTEMS=="scsi",DRIVERS=="sd",ATTRS{vendor}=="Seagate*",ATTRS{model}=="Desktop*",RUN+="/usr/sbin/sdparm --clear STANDBY -6 /dev/%k"
to my udev rules.


Did the problems start occurring after an update/upgrade of
sorts, or is just out of the blue? If your HDD doesn't have the
time-out issue, and if there was no update, a) is most definitely
the case, and I'd be looking at getting a replacement cable and/
or device sooner rather than later.



Cheers,
Tink
 
Old 01-06-2011, 10:28 PM   #5
mike11
Member
 
Registered: Apr 2009
Posts: 222

Original Poster
Rep: Reputation: 17
Thanks Tinkster.

The problems suddenly started about a month or so ago. The drive is about a year old so it seems unlikely to would wear out so quickly. I'm also not sure what can go wrong with the USB cable since there's nothing there which could break/melt etc. .

I install applications regularly with apt-get and it does upgrade existing packages during the process so it may have upgraded rsync or something related which is now causing these issues.

Others have reported the same problem, all when using rsync:
http://linux.derkeiler.com/Mailing-L...5-09/1469.html
http://raywoodcockslatest.blogspot.c...only-file.html

is there some udev/hal/whatever feature which umounts usb drives after a while?.

Thanks.
 
Old 01-06-2011, 10:50 PM   #6
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Mageia, Mint
Posts: 7,731

Rep: Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459Reputation: 1459
I have had my external USB drive occasionally (maybe three or four times in two years) decide that it was read-only.

Unmounting it, disconnecting it, then reconnecting it has always resolved the problem.

I think Tinkster may be on to something as this applies to my experience. It is entirely possible that my USB cable might have gotten jostled or otherwise disturbed, given the physical geography of my laptop area.
 
Old 01-07-2011, 12:02 AM   #7
mike11
Member
 
Registered: Apr 2009
Posts: 222

Original Poster
Rep: Reputation: 17
Thanks Frank.

The problem I've got occurs on daily basis. If the drive isn't being accessed for a while it seems dismount or its permissions change to RO. The drive's usb cable suffers much less jolt than the keyboard and mouse usb cables and the latter two are functioning fine so I'm inclined to think this is not a hardware issue (at least not a cable one).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error: Read-only file system linuxseek Linux - Mobile 2 11-06-2009 09:08 AM
read-only file system error when editing a config file smallfrowne Linux - Newbie 5 02-19-2008 06:06 PM
Read only file system error! xardas Linux - Desktop 1 05-14-2007 10:18 PM
read only file system error surfduke Linux - General 3 09-30-2005 07:04 PM
FC3 boot hang: Read-only file system error? batard Fedora 2 04-05-2005 06:28 AM


All times are GMT -5. The time now is 05:15 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration