Topic: Backup Error

[WF168Tech]

For the last 3 days now, my backup process is reporting this error.

Can't remove file /media/SEAGATE/smeserv.xxx.org/set5/full-201001270200.1.dar (Read-only file system) at /etc/e-smith/events/actions/workstation-backup-dar line 272

SEAGATE is a USB-attached external HD. I'm using the standard backup option in the GUI, backup to USB disk.
Could HD be full? If so, I don't know how to check it.  Thanks for any hints.

[Stefano]

Hi

are you using SME7 or SME8?

there's another post to a similar issue..

please open a bug.

Thank you

[WF168Tech]

I am using SME 7. A few updates need to be applied, maybe 5 or 6, that I have not done yet.

[Stefano]

well, update your server, reboot and try again..

to check how much free space do you have, attach your external hd, mount it and simply give

Code: [Select]

df -h


you should see something like this:

Code: [Select]

[root@esx root]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             4.9G  1.4G  3.3G  29% /
/dev/sda1              99M   27M   68M  29% /boot
none                  132M     0  132M   0% /dev/shm
/dev/sda6             2.0G   47M  1.8G   3% /var/log
//10.0.0.224/backup   929G  569G  361G  62% /mnt/tmp


[WF168Tech]

well, update your server, reboot and try again..

Server updated with all updates. Problem remains. 

[WF168Tech]

I have a new additional message today.

*** No backup allowed or error during backup *** Error while moving backup file /media/SEAGATE/tmp_dir/smeserv.wfschools.org/full-201003310200.1.dar from temporary dir /media/SEAGATE/tmp_dir/smeserv.wfschools.org to /media/SEAGATE/smeserv.wfschools.org/set5 : Read-only file system

[mercyh]

Has this usb drive worked in the past?

It isn't formatted as NTFS by chance? >edit< I can see this isn't the problem as you are creating the temp file.

Either you have permission and ownership problems on the destination directory or the drive does not have enough space hold double the backup size (the temp backup and the final backup location)

I see this is set 5 that you are backing up too. You did not answer the space question asked above.

[WF168Tech]

Has this usb drive worked in the past?       Yes

It isn't formatted as NTFS by chance? >edit< I can see this isn't the problem as you are creating the temp file.   No

Either you have permission and ownership problems on the destination directory or the drive does not have enough space hold double the backup size (the temp backup and the final backup location)   Size=147G, Used=41G, Available=105G

I see this is set 5 that you are backing up too. You did not answer the space question asked above.

Here's the log from my last successful date.

==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup started at Wed Mar  3 02:00:06 2010 Backup of mysql databases has been done Mounting backup shared directory localhost/media/SEAGATE Backup temp directory /media/SEAGATE/tmp_dir/smeserv.wfschools.org is mounted and is writable Using set number 2 of 7 Attempt incremental backup number 6 of 7 Backup base file name is inc-006-201003030200 Making backup in temp directory Using a backup session timeout of : 28770 seconds


 --------------------------------------------
 4742 inode(s) saved
 with 31 hard link(s) recorded
 0 inode(s) changed at the moment of the backup
 194737 inode(s) not saved (no inode/file change)  0 inode(s) failed to save (filesystem error)
 253 inode(s) ignored (excluded by filters)
 1147 inode(s) recorded as deleted from reference backup
 --------------------------------------------
 Total number of inode considered: 200879
 --------------------------------------------
Moving backup files to target directory /media/SEAGATE/smeserv.wfschools.org/set2
Updating backup configuration data
Backup successfully terminated at : Wed Mar  3 02:47:22 2010

[janet]

WF168Tech

Connect the USB backup drive, then login as root to the command prompt and issue the following commands:
mount /media/SEAGATE/
df -h

Make a note of available & used space on the USB drive, it might be shown as sdc depending how many drives you have in the server
Make sure you unmount the drive with
umount /media/SEAGATE/




link=topic=45763.msg223086#msg223086 date=1270052023]
Here's the log from my last successful date.

==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup started at Wed Mar  3 02:00:06 2010 Backup of mysql databases has been done Mounting backup shared directory localhost/media/SEAGATE Backup temp directory /media/SEAGATE/tmp_dir/smeserv.wfschools.org is mounted and is writable Using set number 2 of 7 Attempt incremental backup number 6 of 7 Backup base file name is inc-006-201003030200 Making backup in temp directory Using a backup session timeout of : 28770 seconds


 --------------------------------------------
 4742 inode(s) saved
 with 31 hard link(s) recorded
 0 inode(s) changed at the moment of the backup
 194737 inode(s) not saved (no inode/file change)  0 inode(s) failed to save (filesystem error)
 253 inode(s) ignored (excluded by filters)
 1147 inode(s) recorded as deleted from reference backup
 --------------------------------------------
 Total number of inode considered: 200879
 --------------------------------------------
Moving backup files to target directory /media/SEAGATE/smeserv.wfschools.org/set2
Updating backup configuration data
Backup successfully terminated at : Wed Mar  3 02:47:22 2010
[/quote]

[WF168Tech]

WF168Tech

Connect the USB backup drive, then login as root to the command prompt and issue the following commands:
mount /media/SEAGATE/
df -h

Make a note of available & used space on the USB drive, it might be shown as sdc depending how many drives you have in the server
Make sure you unmount the drive with
umount /media/SEAGATE/

Thank you Mary.  /dev/sdb1  --  Size=147GB, Used=43GB, Available=104GB

[mercyh]

*** No backup allowed or error during backup *** Error while moving backup file /media/SEAGATE/tmp_dir/smeserv.wfschools.org/full-201003310200.1.dar from temporary dir /media/SEAGATE/tmp_dir/smeserv.wfschools.org to /media/SEAGATE/smeserv.wfschools.org/set5 : Read-only file system

Here it looks like the temporary file was created in the ****/tmp_dir/ directory but it is unable to write too the final location in the ***/set5/ directory.

Read-only file system

Can't remove file /media/SEAGATE/smeserv.xxx.org/set5/full-201001270200.1.dar (Read-only file system) at /etc/e-smith/events/actions/workstation-backup-dar line 272

Here it is trying to rotate out the old set and is unable to delete the file, can you delete manually from the command line?

(Read-only file system)

The errors are the same. It would seem that somehow the Dar backup user now longer has write permission on the ***/set5/ directory.

From the command line can you mount the drive and navigate to /media/SEAGATE/tmp_dir/

and issue a:

Code: [Select]

ls -al
to see what permissions are on the files

also on this directory /media/SEAGATE/smeserv.wfschools.org/set5/

Can you manually create a new file in these locations from the command line?

be sure to unmount the drive after you are finished.

[WF168Tech]

Here are the results of: ls -al

drwxr-xr-x  3 root root 4096 Apr  1 02:00 .
drwxr-xr-x  5 root root 4096 Sep 20  2009 ..
drwxr-xr-x  2 root root 4096 Apr  1 02:05 smeserv.wfschools.org

[WF168Tech]

The one I just posted was the results on the tmp_dir directory.
Here are the results on the smeserv.wfschools.org directory.

total 36
drwxr-xr-x  9 root root 4096 Mar 17 03:19 .
drwxr-xr-x  5 root root 4096 Sep 20  2009 ..
drwxr-xr-x  2 root root 4096 Feb 16 02:38 set0
drwxr-xr-x  2 root root 4096 Feb 23 02:41 set1
drwxr-xr-x  2 root root 4096 Mar  3 02:47 set2
drwxr-xr-x  2 root root 4096 Mar 15 02:53 set3
drwxr-xr-x  2 root root 4096 Mar 27 02:41 set4
drwxr-xr-x  2 root root 4096 Feb  2 02:32 set5
drwxr-xr-x  2 root root 4096 Feb  9 02:36 set6

[CharlieBrady]

The errors are the same. It would seem that somehow the Dar backup user now longer has write permission on the ***/set5/ directory.

"Read-only filesystem" means exactly what it says. No file or directory will be writable on the file system, no matter what the permissions are. A file system will be read-only if the hardware is write-protected, if the filesystem was mounted explicitly read-only, and in rarer cases when there is file-system corruption, or internal inconsistency detected in the kernel, due to kernel bugs, RAM problems, or due to file system corruption being detected.

[WF168Tech]

OK, so it appears that my backup sets located on my USB drive have become read-only.  I don't know how or why that happened, and I'm not too sure how to change it.

[mercyh]

The destructive way to test it would be to attempt a reformat of the drive.

[Stefano]

For the last 3 days now, my backup process is reporting this error.

so, something changed on march, 26th.. anything interesting in the logs?
did you change anything on your  usb disk? does it have any kind of write protection switch?

[janet]

WF168Tech

1) Firstly, have you tried unplugging both the USB lead and the power lead from your external USB drive.
Please do so.
Then wait 30 seconds, reconnect power, wait another 30 seconds then reconnect the USB lead.
See if backup will run.

2) For a variety of reasons backups can become corrupted.
Without having diagnosed why or if that is for sure the case here, I'd suggest a file corruption, so it may be simple just to delete set5 and then see what happens.
Of course that older backup set will be lost, so copy it off first if you really must keep it.

mount /media/SEAGATE/
rm /media/SEAGATE/smeserv.wfschools.org/set5/
answer yes as required
umount /media/SEAGATE/

Run backup and see what happens

[CharlieBrady]

2) For a variety of reasons backups can become corrupted.
Without having diagnosed why or if that is for sure the case here, I'd suggest a file corruption, so it may be simple just to delete set5 and then see what happens.

Mary, the file cannot be deleted from a filesystem which is mounted read-only.

There is also no evidence that the file is corrupted.

The file system needs to be unmounted, and the filesystem checked for corruption (or reformatted). Check if the device has a write-protect switch or tab. Check /var/log/messages for anything relevant, especially around March 26th.