similar to: [Bug 12915] New: --modify-window should default to 1 for fat filesystems

https://bugzilla.samba.org/show_bug.cgi?id=12916 Bug ID: 12916 Summary: when rsync fails to chown, it gives up and does not set timestamp Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee:

https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #4 from Kevin Korb <rsync at sanitarium.net> --- The manual says that with FAT you need --modify-window=2 not 1. But here in the US for half of the year you need --modify-window=3602 instead. The same goes for many other locations. The simple fact of the matter is that FAT is an obsolete filesystem designed for 5.25 inch floppy

Does rsync -aAXv /dir1 /dir2, where dir2 is a mounted FAT formatted SD card, and then: rsync -aAXv /dir2 /dir1, to restore the files in dir1 from the FAT formatted SD card, restore the ACL and owner/permissions of the files and directories in dir1? Thanks, John -- John Conover, conover at rahul.net, http://www.johncon.com/

https://bugzilla.samba.org/show_bug.cgi?id=6927 Summary: Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc. Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo:

--no-whole-file would only make it even worse. It would have to read the remote file over the network in order to do the diff then it would write the whole file over the network anyway (--inplace would help a little). Local copies force --whole-file for a good reason. On 03/14/2018 10:05 AM, Ben RUBSON via rsync wrote: > On 14 Mar 2018, Lentes, Bernd via rsync wrote: > >> ----- On

no backup - no mercy ----- On Mar 14, 2018, at 2:19 PM, Ben RUBSON ben.rubson at gmail.com wrote: > On 14 Mar 2018, Lentes, Bernd via rsync wrote: > >> I would now expect a rsync from the snap would transfer just some megay >> bytes to the file from the day before. >> But it doesn't: >> >> ha-idg-1:/cluster/guests/servers_alive # time rsync -av --stats

https://bugzilla.samba.org/show_bug.cgi?id=10738 Summary: report --stats output when termination signal arrives Product: rsync Version: 3.0.9 Platform: x64 OS/Version: Linux Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, rsync v3.0.7 I am backing up data to a USB memory drive that is formatted FAT32, which does not comprehend linux permissions. I added the "--no-perms" option to the option set. rsync still attempts to change the permissions. OPTS = "--no-perms --archive --stats --delete --itemize-changes - --quiet

https://bugzilla.samba.org/show_bug.cgi?id=6928 Summary: Warn the user to use --modify-window=1 --no-owner --no- group etc. on FAT partitions Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo:

Hi All, I feel this is the most simple question but I am currently going around and round in circles and searches keep bringing me up Windows tools!! :-( I have a 512MB USB drive that has a 12MB FAT16 partition on it. How can I resize this 12MB partition to grow and fill the whole 512MB drive? Just in case I am being stupid, here is what I am doing... :-) I would like a quick USB drive that

The `lofiadm'' man page describes how to export a file as a block device and then use `mkfs -F pcfs'' to create a FAT filesystem on it. Can''t I do the same thing by first creating a zvol and then creating a FAT filesystem on it? Nothing I''ve tried seems to work. Isn''t the zvol just another block device? -- -Gary Mills- -Unix Group-

https://bugzilla.samba.org/show_bug.cgi?id=13317 Bug ID: 13317 Summary: rsync returns success when target filesystem is full Product: rsync Version: 3.1.2 Hardware: x64 OS: FreeBSD Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org

Items in dmesg when FAT share's are accessed from web browser: CIFS VFS: bogus file nlink value 0 When accessed from FC/L (OFM (orthodox filemanager)): CIFS VFS: illegal date, month 0 day: 0 When the share is initially mounted: CIFS: Attempting to mount //hostname/E Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers CIFS VFS: Send error

Hi folks, I've been trying to get WINE to run on my new mandrake 8.0 box for _four_ _months_. Every version of WINE gives me: err:dosfs:DRIVE_ReadSuperblock The filesystem is not FAT !! (device=/dev/hda1) when I try to run an app that opens/closes files (e.g. notepad.exe). Software that doesn't use files runs fine (calc.exe) I can read/write to the partition /dev/hda1 just fine...

Hi, I'm running Samba 3.0.23a on Linux. One of my share is a USB disk with a FAT32 filesystem. When copying large files from my Windows XP machine to this share, smbd seem to "reserve" (by using ftruncate()) the space needed on the USB disk before actually doing any copying. This ftruncate() operation takes quite a while when the file is large. It may even cause the client to time

Filesystem UUID shows the partition we boot kernel from. The kernel parameter has format like FSUUID=DA1A-0B2E. The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. The patch is based on 67aaaeeb228. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- com32/include/syslinux/sysappend.h | 1 + core/fs/btrfs/btrfs.c | 3 ++- core/fs/ext2/ext2.c

HI, if I do : [jezequel@soleil tmp]$ rsync -aH /tmp/jppjppjpp ~jezequel/sauvNT chown "/home/jezequel/sauvNT/jppjppjpp" failed: Operation not permitted mkstemp "/home/jezequel/sauvNT/jppjppjpp/.mlkjmlkj.dKl4JR" failed: Operation not permitted chown "/home/jezequel/sauvNT/jppjppjpp" failed: Operation not permitted rsync error: some files could not be transferred (code

This patch adds a switch --fat-filenames which replaces all characters that aren't legal on FAT filesystems with an underscore. This is the first time I touch the rsync code, so I may not be going about it the right way, but it seems to be working. Naturally there's some potential for collisions, but it's probably better than what happens currently (such files are simply not copied).

Is there a mix of SYSLINUX and ISOLINUX that can boot an ISO image from a FAT file system? Sort of like MEMDISK but doesn't need to load the entire great-big ISO into RAM or install an int-13 driver? SYSLINUX would need to be installed on the FAT file system but it would want to chain-load ISOLINUX as installed on the ISO. ISOLINUX would load it's blocks from the ISO file in the FAT

https://bugzilla.samba.org/show_bug.cgi?id=12522 Bug ID: 12522 Summary: [PATCH] Send last error messages to sender Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: