Topic: Backup Error

[geoff]

Thanks to all involved with SME Server for your great work.

Despite upgrading RAM and motherboard, and changing the USB Backup drive I keep getting this error. Should it be a bug?

Error while saving data: Cannot write down the archive: Error while writing to file: Read-only file system SANITY CHECK: AT LEAST ONE THREAD_CANCELLATION OBJECT HAS NOT BEEN DESTROYED AND REMAINS IN MEMORY WHILE THE PROGRAM REACHED ITS END ###################################################################
  SPECIAL ALLOCATION MODULE REPORTS UNRELEASED MEMORY ALLOCATIONS

Dumping list for blocks of 60 bytes size
   1 cluster(s) contain unreleased blocks of memory:
      Cluster dump:
         block_size           = 60
         available_blocks      = 191
         max_available_blocks = 192
         which makes 1 unreleased block(s)
         Follows the list of unreleased blocks for that cluster:
                 unreleased memory (60 bytes) at: 0x9ec1c88


###################################################################
Error while running dar: 5 at /etc/e-smith/events/actions/workstation-backup-dar line 505.
Backup terminated: backup failed - status: 7424

[janet]

geoff

Is that dar error code 5 (on the second last line of your post),
See here for clues.
http://forums.contribs.org/index.php?topic=39887.0

Where & when do you keep getting the error message ?

Have you reviewed the log files, starting with /var/log/messages ?

Most probably you should report this as a bug for a more formal review & analysis, link at top of forums.

[geoff]

Thank you for your reply, Janet.

The error happens when a full scheduled backup runs, every time but a backup from the Configuration screen works fine. (Option .

I've tested (and replaced RAM) and upgraded the motherboard but the message remains the same.

It looks like an application error to me but I'm happy to be proved wrong.

I'll post a bug.

Thanks again.

[geoff]

Thanks, Charlie, for your reply on the Bug I posted.

All the drives I used for backup have been formatted Ext3.

The first Seagate backup drive to give this error has checked out perfectly using Seatools and formats and saves Windows files perfectly, although the second, WD drive failed.

The third new Seagate drive in the original NexStar3 USB housing works fine. Weird.

Thank you for your help.

[janet]

For the forum record, see Bug 8186
The issue was a faulty drive as per previous post.

[geoff]

Thank you, Janet.

Charlie gave this reference:

http://alienghic.livejournal.com/382903.html

I'll reformat the original drive on another machine, try it and report.

Thanks for the support.