On Sun, Mar 04, 2012 at 09:47:24AM -0500, Jiri B wrote: > Hello, > > I have a script which mount read-write a filesystem and then > runs rsync to synchronize. The strange thing is, that although > the filesystem is read-write for the OS, rsync still has some > problem with that. > > %>--- > > + mount > + grep /dev/sd0f > /dev/sd0f on /mfs/log type ffs (local, nodev, noexec, nosuid, read-only) > + mount -uw /dev/sd0f > + mount > + grep /dev/sd0f > /dev/sd0f on /mfs/log type ffs (local, nodev, noexec, nosuid) > + printf Synchronizing in memory /var/log to /log backup ... > Synchronizing in memory /var/log to /log backup ... + /usr/local/bin/rsync > -vhaz /var/log/ /mfs/log/ > sending incremental file list > pflog > rsync: mkstemp "/mfs/log/.pflog.czoYN2" failed: Read-only file system (30) > > sent 5.96K bytes received 34 bytes 11.99K bytes/sec > total size is 2.62M speedup is 437.81 > rsync error: some files/attrs were not transferred (see previous errors) > (code 23) at main.c(1052) [sender=3.0.9] > + mount -ur /dev/sd0f
Cardinal mistake: you're showing us what you think is happening, not the real shit. The only way to know if you can write to /mfs/log is to try to write something there, with touch, for instance. Right now, I would tend to think your setup is bogus. or maybe it's a bug in rsync ? There's no simple way for us to know, but it is incredibly easy for you to check. Second mistake: not giving all the information. What's the sense of doing mount|grep ? you're afraid we're going to poke fun at you because you do strange things ?
