Displaying 20 results from an estimated 5000 matches similar to: "vfat / ftruncate problem"
2007 Sep 22
4
VFAT filesystem and large files
Hello
I have used samba for many years, and it worked great (thanks!).
Anyway, I recently decided to add a USB drive to the server.
Currently running 2.6.29.2 linux kernel, debian etch.
samba version 3.0.24
The USB drive is VFAT
I am able to write small files remotely to the USB drive (a few Kb, 10's of Kb) without a problem.
However, whenever I try to write something "larger"
2001 Feb 14
1
Samba newbie problems
Hi
I have recently installed samba on a RH7.0 box. This box has win98 +
linux rh7 installed and both os's are running well. The F drive on
windows is FAT32 and is mounted r/w on linux RH7. Works fine.
I also have a Win98se machine that needs to have full read/write access
to some partitions on the RH7 box. Samba was found ideal for such setup.
The problem I have is that I can't write to
2001 Aug 15
1
vfat is not working with ext3 patch
Hi all,
My system is :
kernel 2.4.8 with ext3-0.9.6 patch
e2fsprogs-1.22-2, mount-2.11g, util-linux-2.11f
And ext3 filesystem works fine, but when a vfat partition is mounted:
[fargo] [~] # mount /dev/hdd1 /mnt/tmp
[fargo] [~] # mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hdd1 on /mnt/tmp type vfat (rw)
everything looks
2007 May 17
1
Possible? Mount vfat, share, have full use of R/A/S/H attributes?
Hi, I've tried a couple of different versions/distros and can't seem to
mount a FAT32 (vfat) partition and then share it with Samba, such that
all use of R/A/S/H attributes (for files and folder) is maintained...
So I'm wondering if this is even possible?
I've most recently been testing with
host: Debian 4.0 (Linux 2.6.18-4-686) which includes Samba 3.0.24
client: WinXP
2018 Sep 05
0
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
>
> Here's a fun one:
>
> + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit
> + virt-sparsify --in-place test-virt-sparsify-in-place-fstrim-unsupported.img
> + tee test-virt-sparsify-in-place-fstrim-unsupported.log
> [ 2.4] Trimming /dev/sda1
> [ 7.5] Sparsify in-place
2018 Sep 05
0
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:45:51PM +0100, Richard W.M. Jones wrote:
> On Wed, Sep 05, 2018 at 04:41:01PM +0100, Daniel P. Berrangé wrote:
> > On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
> > >
> > > Here's a fun one:
> > >
> > > + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit
> > > +
2018 Sep 05
1
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:53:03PM +0100, Daniel P. Berrangé wrote:
> On Wed, Sep 05, 2018 at 04:45:51PM +0100, Richard W.M. Jones wrote:
> > On Wed, Sep 05, 2018 at 04:41:01PM +0100, Daniel P. Berrangé wrote:
> > > On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
> > > >
> > > > Here's a fun one:
> > > >
> > >
2009 Aug 08
0
Samba, OSX, and USB vfat
OK. I'll setup the scenario.
I'm trying to use a USB Vfat drive shared via samba to an OSX 10.5.8 client.
When copying files from the Mac to Samba 3.0.26a I kept getting this error:
You do not have sufficient privileges to complete this operation (or
something close to
that)
And it would not complete the copy operation.
This is resolved for the moment, but wanted to share some of
2004 Aug 18
0
[Bug 1605] New: Copy from NTFS to VFAT produces mkstemp and stat errors
https://bugzilla.samba.org/show_bug.cgi?id=1605
Summary: Copy from NTFS to VFAT produces mkstemp and stat errors
Product: rsync
Version: 2.6.2
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy:
2018 Jan 16
0
How should I be using rsync with FAT32/VFAT
#1 yes, you should use -rt instead of -a as everything else in -a is
incompatible with vfat.
#2 timestamps will always be a problem on vfat. It has a 1 or 2 second
resolution so --modify-window=2 is a common solution. However, if you
live somewhere that has yearly clock changes (we call it daylight
savings time) those will cause the timestamps to be off by an hour on
top of the 1-2 second
2008 Jun 17
1
Strange Samba permissions on vfat (fat32) volume
I'm running Samba on Ubuntu server. I know, perhaps it is not related with Ubuntu Server 8.04, but rather
with Samba itself, but I thought perhaps someone has similar
experience...
I have a couple of shares on Samba on a vfat (fat32) volume. As
everybody knows Linux permissions does not work on vfat, except on
mount folder where vfat partition is mounted. I though that is really
not a
2024 Jan 21
1
Archiving to vfat
it's most likely because of vfat timestamp limitation
try
--modify-window
????????????? When comparing two timestamps, rsync treats the
timestamps as being equal if they differ by no more than? the modify-window
????????????? value.?? This? is? normally? 0 (for an exact match), but
you may find it useful to set this to a larger value in some situa-
????????????? tions.? In particular,
2018 Jan 16
0
How should I be using rsync with FAT32/VFAT
You don't have to change the system setting just change the TZ env
variable in the terminal you run rsync in.
On 01/16/2018 01:30 PM, John Long via rsync wrote:
> Thanks a lot, Kevin.
>
> I have a new Linux box and tried to set it to UTC but I think gnome
> outsmarted me...
>
> I'll use -rt and maybe ignore timestamps entirely rather than the
> window. If I find
2005 Apr 12
1
Writing to a vfat partition problem
Hi all,
I have a problem where when I try to write to a 'vfat' partition (in
Fedora Core 3, rsync 2.6.3) I get this error:
-=-=-[ error ]-=-=-
rsync: mkdir
"/mnt/tle-bu/src0/tle-bu/231e2838-93b0-4f6f-8b8b-f09e24e1ed80" failed:
No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(381)
rsync: connection unexpectedly closed (8 bytes received so
2005 Sep 03
3
Accents in filenames on vfat filesystem
Hello.
I am trying to create a text file that contains an accent like '?' in it's
filename on a vfat filesystem. This generates an error like the following:
"test?.txt" E212: Can't open file for writing
I have made a 'modprobe nls_cp850' and 'modprobe nls_iso8859-1' to load
those needed modules.
Then I mounted my FAT32 partition like this:
mount -t
2005 Jan 04
1
date problem with ntfs or vfat mounted file sytem
Hi
under linux I have to mount windows filesystem (ntfs or vfat).
but with rsync (or with a single touch command as well) I can not
write a file with a correct date on /mnt/windows_vfat or
/mnt/windows_ntfs
with ntfs --> only write file system !
with vfat --> wrong date ! so rsync does a full copy each time.
How can I solve this ?
PS: I use the same script to synchronise ext3 filesystem as
2024 Jan 21
2
Archiving to vfat
I am trying to use rsync between two local directories on Linux.
The source directory is on a normal ext4 partition, under my home
directory. The destination is an SD card that I insert into the card
reader on the computer, formatted with a vfat filesystem.
The command line is like
rsync -avC --delete /home/itz/foo/ /media/itz/DEAD-BEEF/foo/
This does not work as I expected: all files are
2005 Jan 10
1
Sharing a vfat partition
Hi Everybody!
I'm sharing my VFAT partition on computer #1.
Computer #2 can both read and write stuff on computer #1, but every
once in a while - could be like 1 in 3 - my XP on computer #2 will
say "file system error". The second error will say something about
the file being locked.
Then I changed my smb.conf to make samba say that my share
was a FAT (instead of NTFS) and I
2018 Sep 05
2
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:41:01PM +0100, Daniel P. Berrangé wrote:
> On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
> >
> > Here's a fun one:
> >
> > + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit
> > + virt-sparsify --in-place test-virt-sparsify-in-place-fstrim-unsupported.img
> > + tee
2018 Sep 05
3
Tests and trimming vfat
Here's a fun one:
+ guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit
+ virt-sparsify --in-place test-virt-sparsify-in-place-fstrim-unsupported.img
+ tee test-virt-sparsify-in-place-fstrim-unsupported.log
[ 2.4] Trimming /dev/sda1
[ 7.5] Sparsify in-place operation completed with no errors
+ grep 'warning:.*fstrim'