Re: ftruncate returning EPERM on vfat filesystem

2001-01-07 Thread Richard Henderson
On Sun, Jan 07, 2001 at 01:55:15PM +, Alan Cox wrote: > > + return -EPERM; > > To stop a case where the fs gets corrupted otherwise. You can change that to > return 0 which is more correct but most not remove it. While I suppose "0" is covered under "the result is unspe

Re: ftruncate returning EPERM on vfat filesystem

2001-01-07 Thread Daniel Phillips
Alan Cox wrote: > > > + > > + /* FAT cannot truncate to a longer file */ > > + if (attr->ia_valid & ATTR_SIZE) { > > + if (attr->ia_size > inode->i_size) > > + return -EPERM; > > + } > > > > error = inode_change_ok(inode, attr); > >

Re: ftruncate returning EPERM on vfat filesystem

2001-01-07 Thread Dave
Hi Alan, On Sun, 7 Jan 2001, Alan Cox wrote: > I wrote: > > + > > + /* FAT cannot truncate to a longer file */ > > + if (attr->ia_valid & ATTR_SIZE) { > > + if (attr->ia_size > inode->i_size) > > + return -EPERM; > > + } > > > > erro

Re: ftruncate returning EPERM on vfat filesystem

2001-01-07 Thread Alan Cox
> + > + /* FAT cannot truncate to a longer file */ > + if (attr->ia_valid & ATTR_SIZE) { > + if (attr->ia_size > inode->i_size) > + return -EPERM; > + } > > error = inode_change_ok(inode, attr); > if (error) > > Can someone te

ftruncate returning EPERM on vfat filesystem

2001-01-06 Thread Dave
Hi everyone, I experienced a strange problem after upgrading from 2.4.0-test12 to the 2.4.0 kernel. My samba configuration stopped working. Reverting back to 2.4.0-test12, it magically starts working again. (2.4.0 also hard-locked my machine before I noticed this problem, but I'll report that