From: Papp T. <to...@ma...> - 2011-05-20 09:16:12
|
hi! My server looks really weird. $ df |grep backup ;echo $? 1 $ df /data/backup Filesystem 1K-blocks Used Available Use% Mounted on mfsmaster:9421 0 0 0 - /data/backup $ mount |grep /data/backup mfsmaster:9421 on /data/backup type fuse.mfs (rw,nosuid,nodev,allow_other,default_permissions) This is a drivish backup pool. There are success and unsuccess backups. I see rsync errors, like this: *** Execution cycle 0 *** rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: close failed on "/data/backup/cluster/replicated/2011-05-20--04-00/tree/15_DY/40_2D/Admin/Utilities/contact_sheet/.contact_sheet_render_CHK.nk.kQ7WgQ": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(731) [receiver=3.0.7] rsync: connection unexpectedly closed (12188 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7] There are other errors too with no log file, dirvish job died somewehere else... The chunk has free space ('cluster' has van chunk): /dev/sda6 10T 6.9T 3.1T 70% /mnt/mfschunk1 Also now I see the the mount point: mfsmaster:9421 10T 6.9T 3.1T 70% /data/backup In the logs I don't see any special messages except it says, no metaloggers connected, although metalogger is running. The system is Ubuntu Natty with lucid based packages from ppa. I still didn't recompile them. No I will, but I'm not sure, does it cause this? Thank you, tamas |