SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
strange read-only file error
Author Message
Post strange read-only file error 
I'm getting this huge set of error messages, most of which I don't
understand. There's a "read-only file system" line which seems to be
intelligible but I have no idea why it appears. I'm plugging in my
external HDD the same way I did last time, when rdiff-backup ran fine,
and the 'mount' command shows this for the backup file system,
"/dev/sdb1 on /media/b080d187-ad00-4b4a-9721-fcbe5e839827 type ext3
(rw,nosuid,nodev,uhelper=devkit)"--ie, it's presumably mounted 'rw'.

Here's the whole set of messages (I tried to run the rdiff-backup twice
and got slightly different results, but no success.) Hopefully someone
can help me on this.

======
eric < at > linux-7fva:~> su
Password:
linux-7fva:/home/eric # rdiff-backup
--exclude /home/eric/.evolution/cache/tmp --include /home/eric
--include /var/www --include /var/lib/mysql --include /srv --exclude
'**' / /media/b080d187-ad00-4b4a-9721-fcbe5e839827/openSUSE11.2Backup

SpecialFileError home/eric/.config/google-chrome/SingletonSocket Socket
error: AF_UNIX path too long
ListError home/eric/.gtk-bookmarks/.gvfs [Errno 13] Permission denied:
'/home/eric/.gvfs'
IOError while trying to log exception!
Exception '[Errno 30] Read-only file system' raised of class '<type
'exceptions.IOError'>':
File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line
32, in check_common_error
try: return function(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Rdiff.py", line
98, in patch_local
if outrp: return outrp.write_from_fileobj(patchfile)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1195, in write_from_fileobj
copyfileobj(fp, outfp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
64, in copyfileobj
outputfp.write(inbuf)


Message from syslogd < at > linux-7fva at Jun 21 06:32:23 ...
kernel:[121311.947209] journal commit I/O error
Exception '[Errno 30] Read-only file system' raised of class '<type
'exceptions.IOError'>':
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
343, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
51, in Mirror_and_increment
DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
243, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rorpiter.py",
line 281, in __call__
last_branch.fast_process(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
692, in fast_process
if self.patch_to_temp(mirror_rp, diff_rorp, tf):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
556, in patch_to_temp
elif not self.patch_diff_to_temp(basis_rp, diff_rorp, new):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
592, in patch_diff_to_temp
Rdiff.patch_local, (basis_rp, diff_rorp, new))
File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line
32, in check_common_error
try: return function(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Rdiff.py", line
98, in patch_local
if outrp: return outrp.write_from_fileobj(patchfile)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1195, in write_from_fileobj
copyfileobj(fp, outfp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
64, in copyfileobj
outputfp.write(inbuf)

Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 30, in <module>
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
343, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
51, in Mirror_and_increment
DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
243, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rorpiter.py",
line 281, in __call__
last_branch.fast_process(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
692, in fast_process
if self.patch_to_temp(mirror_rp, diff_rorp, tf):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
556, in patch_to_temp
elif not self.patch_diff_to_temp(basis_rp, diff_rorp, new):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
592, in patch_diff_to_temp
Rdiff.patch_local, (basis_rp, diff_rorp, new))
File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line
32, in check_common_error
try: return function(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Rdiff.py", line
98, in patch_local
if outrp: return outrp.write_from_fileobj(patchfile)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1195, in write_from_fileobj
copyfileobj(fp, outfp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
64, in copyfileobj
outputfp.write(inbuf)
IOError: [Errno 30] Read-only file system
close failed in file object destructor:
IOError: [Errno 30] Read-only file system
close failed in file object destructor:
IOError: [Errno 30] Read-only file system
You have new mail in /var/spool/mail/eric
linux-7fva:/home/eric #
linux-7fva:/home/eric # rdiff-backup
--exclude /home/eric/.evolution/cache/tmp --include /home/eric
--include /var/www --include /var/lib/mysql --include /srv --exclude
'**' / /media/b080d187-ad00-4b4a-9721-fcbe5e839827/openSUSE11.2Backup
Previous backup seems to have failed, regressing destination now.
Warning: Could not restore file home/eric/Eric
Jobs/11468659522-CraigsList!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None. Instead of the actual file's data, an empty length file will be
created. This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
Exception '[Errno 5] Input/output error' raised of class '<type
'exceptions.OSError'>':
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
342, in Backup
rpout.conn.Main.backup_touch_curmirror_local(rpin, rpout)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
523, in backup_touch_curmirror_local
mirrorrp.fsync_with_dir()
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1314, in fsync_with_dir
self.fsync(fp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1276, in fsync
if not fp: self.conn.rpath.RPath.fsync_local(self)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1289, in fsync_local
os.fsync(fd)


Message from syslogd < at > linux-7fva at Jun 21 07:13:47 ...
kernel:[123795.695683] journal commit I/O error
Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 30, in <module>
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
342, in Backup
rpout.conn.Main.backup_touch_curmirror_local(rpin, rpout)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
523, in backup_touch_curmirror_local
mirrorrp.fsync_with_dir()
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1314, in fsync_with_dir
self.fsync(fp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1276, in fsync
if not fp: self.conn.rpath.RPath.fsync_local(self)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1289, in fsync_local
os.fsync(fd)
OSError: [Errno 5] Input/output error
linux-7fva:/home/eric #
============

Thanks



_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
Well I rebooted and then it ran fine. Does that mean it is _necessary_
to run rdiff-backup with a "clean" boot, or does anyone have some other
explanation for the errors I got?

Thanks


On Mon, 2010-06-21 at 07:27 -0400, Eric Beversluis wrote:
I'm getting this huge set of error messages, most of which I don't
understand. There's a "read-only file system" line which seems to be
intelligible but I have no idea why it appears. I'm plugging in my
external HDD the same way I did last time, when rdiff-backup ran fine,
and the 'mount' command shows this for the backup file system,
"/dev/sdb1 on /media/b080d187-ad00-4b4a-9721-fcbe5e839827 type ext3
(rw,nosuid,nodev,uhelper=devkit)"--ie, it's presumably mounted 'rw'.

Here's the whole set of messages (I tried to run the rdiff-backup twice
and got slightly different results, but no success.) Hopefully someone
can help me on this.

======
eric < at > linux-7fva:~> su
Password:
linux-7fva:/home/eric # rdiff-backup
--exclude /home/eric/.evolution/cache/tmp --include /home/eric
--include /var/www --include /var/lib/mysql --include /srv --exclude
'**' / /media/b080d187-ad00-4b4a-9721-fcbe5e839827/openSUSE11.2Backup

SpecialFileError home/eric/.config/google-chrome/SingletonSocket Socket
error: AF_UNIX path too long
ListError home/eric/.gtk-bookmarks/.gvfs [Errno 13] Permission denied:
'/home/eric/.gvfs'
IOError while trying to log exception!
Exception '[Errno 30] Read-only file system' raised of class '<type
'exceptions.IOError'>':
File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line
32, in check_common_error
try: return function(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Rdiff.py", line
98, in patch_local
if outrp: return outrp.write_from_fileobj(patchfile)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1195, in write_from_fileobj
copyfileobj(fp, outfp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
64, in copyfileobj
outputfp.write(inbuf)


Message from syslogd < at > linux-7fva at Jun 21 06:32:23 ...
kernel:[121311.947209] journal commit I/O error
Exception '[Errno 30] Read-only file system' raised of class '<type
'exceptions.IOError'>':
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
343, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
51, in Mirror_and_increment
DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
243, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rorpiter.py",
line 281, in __call__
last_branch.fast_process(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
692, in fast_process
if self.patch_to_temp(mirror_rp, diff_rorp, tf):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
556, in patch_to_temp
elif not self.patch_diff_to_temp(basis_rp, diff_rorp, new):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
592, in patch_diff_to_temp
Rdiff.patch_local, (basis_rp, diff_rorp, new))
File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line
32, in check_common_error
try: return function(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Rdiff.py", line
98, in patch_local
if outrp: return outrp.write_from_fileobj(patchfile)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1195, in write_from_fileobj
copyfileobj(fp, outfp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
64, in copyfileobj
outputfp.write(inbuf)

Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 30, in <module>
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
343, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
51, in Mirror_and_increment
DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
243, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rorpiter.py",
line 281, in __call__
last_branch.fast_process(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
692, in fast_process
if self.patch_to_temp(mirror_rp, diff_rorp, tf):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
556, in patch_to_temp
elif not self.patch_diff_to_temp(basis_rp, diff_rorp, new):
File "/usr/lib64/python2.6/site-packages/rdiff_backup/backup.py", line
592, in patch_diff_to_temp
Rdiff.patch_local, (basis_rp, diff_rorp, new))
File "/usr/lib64/python2.6/site-packages/rdiff_backup/robust.py", line
32, in check_common_error
try: return function(*args)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Rdiff.py", line
98, in patch_local
if outrp: return outrp.write_from_fileobj(patchfile)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1195, in write_from_fileobj
copyfileobj(fp, outfp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
64, in copyfileobj
outputfp.write(inbuf)
IOError: [Errno 30] Read-only file system
close failed in file object destructor:
IOError: [Errno 30] Read-only file system
close failed in file object destructor:
IOError: [Errno 30] Read-only file system
You have new mail in /var/spool/mail/eric
linux-7fva:/home/eric #
linux-7fva:/home/eric # rdiff-backup
--exclude /home/eric/.evolution/cache/tmp --include /home/eric
--include /var/www --include /var/lib/mysql --include /srv --exclude
'**' / /media/b080d187-ad00-4b4a-9721-fcbe5e839827/openSUSE11.2Backup
Previous backup seems to have failed, regressing destination now.
Warning: Could not restore file home/eric/Eric
Jobs/11468659522-CraigsList!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None. Instead of the actual file's data, an empty length file will be
created. This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
Exception '[Errno 5] Input/output error' raised of class '<type
'exceptions.OSError'>':
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
342, in Backup
rpout.conn.Main.backup_touch_curmirror_local(rpin, rpout)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
523, in backup_touch_curmirror_local
mirrorrp.fsync_with_dir()
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1314, in fsync_with_dir
self.fsync(fp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1276, in fsync
if not fp: self.conn.rpath.RPath.fsync_local(self)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1289, in fsync_local
os.fsync(fd)


Message from syslogd < at > linux-7fva at Jun 21 07:13:47 ...
kernel:[123795.695683] journal commit I/O error
Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 30, in <module>
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
304, in error_check_Main
try: Main(arglist)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
324, in Main
take_action(rps)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
280, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
342, in Backup
rpout.conn.Main.backup_touch_curmirror_local(rpin, rpout)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/Main.py", line
523, in backup_touch_curmirror_local
mirrorrp.fsync_with_dir()
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1314, in fsync_with_dir
self.fsync(fp)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1276, in fsync
if not fp: self.conn.rpath.RPath.fsync_local(self)
File "/usr/lib64/python2.6/site-packages/rdiff_backup/rpath.py", line
1289, in fsync_local
os.fsync(fd)
OSError: [Errno 5] Input/output error
linux-7fva:/home/eric #
============

Thanks



_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki



_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
Hi Eric,

On 2010-06-21 19:39, Eric Beversluis wrote:
Well I rebooted and then it ran fine. Does that mean it is _necessary_
to run rdiff-backup with a "clean" boot, or does anyone have some other
explanation for the errors I got?

Thanks


On Mon, 2010-06-21 at 07:27 -0400, Eric Beversluis wrote:
I'm getting this huge set of error messages, most of which I don't
understand. There's a "read-only file system" line which seems to be
intelligible but I have no idea why it appears. I'm plugging in my
external HDD the same way I did last time, when rdiff-backup ran fine,
and the 'mount' command shows this for the backup file system,
"/dev/sdb1 on /media/b080d187-ad00-4b4a-9721-fcbe5e839827 type ext3
(rw,nosuid,nodev,uhelper=devkit)"--ie, it's presumably mounted 'rw'.

Here's the whole set of messages (I tried to run the rdiff-backup twice
and got slightly different results, but no success.) Hopefully someone
can help me on this.
[...]

I had this kind of "read-only file system" errors recently. Then I
noticed that the 3.5" external USB drive was not plugged in properly,
and had lost power during the backup.

Maybe that's what happened during your backup? Or the connection to the
drive was lost in some other way?

Patrick.

--
Key ID: 0x86E346D4 http://patrick-nagel.net/key.asc
Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4


_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
On 21/06/10 13:39, Eric Beversluis wrote:
Well I rebooted and then it ran fine. Does that mean it is _necessary_
to run rdiff-backup with a "clean" boot, or does anyone have some other
explanation for the errors I got?

Thanks

eric < at > linux-7fva:~> su
linux-7fva:/home/eric # rdiff-backup
ListError home/eric/.gtk-bookmarks/.gvfs [Errno 13] Permission denied:


When the reboot fixed this, the problem is the ".gvfs" virtual
filesystem - the reboot got rid of it (I guess it will be automatically
mounted again when you do something with you bookmarks). This virtual
filesystem can not even be accessed as root, that's why you get the
error above.

Add --exclude-other-filesystems to the command line to skip those
virtual filesystems, the contents are not meant to be backed up, anyway.


Jakob

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
On Mon, Jun 21, 2010 at 07:27:28AM -0400, Eric Beversluis wrote:
I'm getting this huge set of error messages, most of which I don't
understand. There's a "read-only file system" line which seems to be
intelligible but I have no idea why it appears.

I hope I'm not teaching you to suck eggs, but filesystems are often
remounted read-only automatically if the OS encounters errors while
writing. It sounds like that happened to your drive mid-backup, and that's
why rebooting fixed it – it got mounted as normal as part of the boot
process.

It sounds like your backup drive is becoming more unreliable (which is a
less dramatic way of saying "could be about to fail"), which is why it
happened at different points in your backup. USB also has limits to the
amount of data it can simultaneously transfer, so if you're doing a lot of
other USB-centric stuff at the same time as your backup this could also be
a problem.

If you have a second system you can plug your external drive into, you
could do some tests to confirm it is the drive that's causing problems.


Hope this helps,

--
Alex Pounds .~. http://www.alexpounds.com/
/V\ http://www.ethicsgirls.com/
// \\
"Variables won't; Constants aren't" /( )\
^`~'^

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
On Jun 22, 2010, at 5:40 PM, Alex Pounds wrote:

On Mon, Jun 21, 2010 at 07:27:28AM -0400, Eric Beversluis wrote:
I'm getting this huge set of error messages, most of which I don't
understand. There's a "read-only file system" line which seems to be
intelligible but I have no idea why it appears.

I hope I'm not teaching you to suck eggs, but filesystems are often
remounted read-only automatically if the OS encounters errors while
writing. It sounds like that happened to your drive mid-backup, and that's
why rebooting fixed it – it got mounted as normal as part of the boot
process.

.gvfs is a fuse mount point. Only the user that mounted it has permission to access it. Not even root does.

So, while your point is valid for standard filesystems, there's no need to scare for this instance. Very Happy

Regards,
Luc
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
On Tue, Jun 22, 2010 at 05:43:45PM +0200, Luciano Rocha wrote:
On Jun 22, 2010, at 5:40 PM, Alex Pounds wrote:
I hope I'm not teaching you to suck eggs, but filesystems are often
remounted read-only automatically if the OS encounters errors while
writing.

.gvfs is a fuse mount point. Only the user that mounted it has
permission to access it. Not even root does. So, while your point is
valid for standard filesystems, there's no need to scare for this
instance. Very Happy

Sure, but I don't think the .gvfs error is related to the eventual failure
of the backup. Instead, it's a result of Eric backing up his home
directory (which includes a .gvfs directory that has the permissions set
as you describe). The traceback doesn't include a log of what file
rdiff-backup was attempting to back up, but the syslog excerpt given by
the OP includes a "journal commit I/O error" and incorrect permissions
wouldn't result in a previously writable filesystem being remounted as
read-only.

--
Alex Pounds .~. http://www.alexpounds.com/
/V\ http://www.ethicsgirls.com/
// \\
"Variables won't; Constants aren't" /( )\
^`~'^

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
The discussion is getting interesting. Thanks.

In previous rdiff backups, the .gvfs file was simply ignored. So I don't
think this could have caused the problem.

External HDD could be the problem. I had serious trouble with a WD
Passport because of some crap on it that couldn't be removed and
basically wouldn't let me use it with Linux (and WD was very snotty
about not providing Linux support for their HDDs). Now I'm using a USB
Toshiba drive (same small size as Passport). I may need to use my
Y-cable to get appropriate and consistent power for it?

On Wed, 2010-06-23 at 00:04 +0100, Alex Pounds wrote:
On Tue, Jun 22, 2010 at 05:43:45PM +0200, Luciano Rocha wrote:
On Jun 22, 2010, at 5:40 PM, Alex Pounds wrote:
I hope I'm not teaching you to suck eggs, but filesystems are often
remounted read-only automatically if the OS encounters errors while
writing.

.gvfs is a fuse mount point. Only the user that mounted it has
permission to access it. Not even root does. So, while your point is
valid for standard filesystems, there's no need to scare for this
instance. Very Happy

Sure, but I don't think the .gvfs error is related to the eventual failure
of the backup. Instead, it's a result of Eric backing up his home
directory (which includes a .gvfs directory that has the permissions set
as you describe). The traceback doesn't include a log of what file
rdiff-backup was attempting to back up, but the syslog excerpt given by
the OP includes a "journal commit I/O error" and incorrect permissions
wouldn't result in a previously writable filesystem being remounted as
read-only.




_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Post strange read-only file error 
On 23/06/10 01:32, Eric Beversluis wrote:
The discussion is getting interesting. Thanks.

In previous rdiff backups, the .gvfs file was simply ignored. So I don't
think this could have caused the problem.

I didn't notice this one,
Message from syslogd < at > linux-7fva at Jun 21 06:32:23 ...
kernel:[121311.947209] journal commit I/O error
that's some more serious problem.
You should have more info saved in the syslog file.

External HDD could be the problem. I had serious trouble with a WD
Passport because of some crap on it that couldn't be removed and
basically wouldn't let me use it with Linux (and WD was very snotty
about not providing Linux support for their HDDs). Now I'm using a USB
Toshiba drive (same small size as Passport). I may need to use my
Y-cable to get appropriate and consistent power for it?

While I don't know about the black magic of Y-cables, I'd take a look at
the smart data of the drive, esp. Current_Pending_Sector and
Reallocated_Sector_Ct . If it has more than a few bad sectors I'd try to
RMA the drive.
You may need additional switches for smartctl to get it to work over
USB:
http://sourceforge.net/apps/trac/smartmontools/wiki/Supported_USB-Devices (and
it may not work at all, unfortuanately, though there are some Toshibas
in the list)


On Wed, 2010-06-23 at 00:04 +0100, Alex Pounds wrote:
On Tue, Jun 22, 2010 at 05:43:45PM +0200, Luciano Rocha wrote:
On Jun 22, 2010, at 5:40 PM, Alex Pounds wrote:
I hope I'm not teaching you to suck eggs, but filesystems are often
remounted read-only automatically if the OS encounters errors while
writing.

.gvfs is a fuse mount point. Only the user that mounted it has
permission to access it. Not even root does. So, while your point is
valid for standard filesystems, there's no need to scare for this
instance. Very Happy

Sure, but I don't think the .gvfs error is related to the eventual failure
of the backup. Instead, it's a result of Eric backing up his home
directory (which includes a .gvfs directory that has the permissions set
as you describe). The traceback doesn't include a log of what file
rdiff-backup was attempting to back up, but the syslog excerpt given by
the OP includes a "journal commit I/O error" and incorrect permissions
wouldn't result in a previously writable filesystem being remounted as
read-only.




_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB