On May 14 10:33, Jeremy Allison wrote:
> On Sat, May 12, 2012 at 12:53:49PM +0200, Corinna Vinschen wrote:
> > On May 11 14:15, Jeremy Allison wrote:
> > > The get_FileIndex() code has been there since at least 3.6.x, but
> > > I'll try and track down when it was first introduced.
> >
> > That wou
On Sat, May 12, 2012 at 12:53:49PM +0200, Corinna Vinschen wrote:
> Hi Jeremy,
>
> On May 11 14:15, Jeremy Allison wrote:
> > On Fri, May 11, 2012 at 07:58:43PM +0200, Corinna Vinschen wrote:
> > > On May 11 12:56, starlight.201...@binnacle.cx wrote:
> > > > /**
Hi Jeremy,
On May 11 14:15, Jeremy Allison wrote:
> On Fri, May 11, 2012 at 07:58:43PM +0200, Corinna Vinschen wrote:
> > On May 11 12:56, starlight.201...@binnacle.cx wrote:
> > > /
> > > Create a 64 bit FileIndex. If the file i
On Fri, May 11, 2012 at 07:58:43PM +0200, Corinna Vinschen wrote:
> On May 11 12:56, starlight.201...@binnacle.cx wrote:
> > Here is the logic Samba uses for inode
> > determination, per Jermey Allison:
> >
> >
> >
> > Ok, here's how we construct the 64-bit return
> > value for that field:
> >
At 07:58 PM 5/11/2012 +0200, Corinna Vinschen wrote:
>Which Samba version introduced this behaviour?
Don't know.
I'm stepping aside on this now. Just
reported it since it came up and broke
a script we have. I've worked around
the inode test by comparing 'sha1sum'
values for the files and re-har
On May 11 12:56, starlight.201...@binnacle.cx wrote:
> Here is the logic Samba uses for inode
> determination, per Jermey Allison:
>
>
>
> Ok, here's how we construct the 64-bit return
> value for that field:
>
> /
> Create a
Here is the logic Samba uses for inode
determination, per Jermey Allison:
Ok, here's how we construct the 64-bit return
value for that field:
/
Create a 64 bit FileIndex. If the file is on the same device as
the root of the s
At 06:23 PM 5/11/2012 +0200, Corinna Vinschen wrote:
>Additionally, the returned file ID must be > 0x,
>otherwise we don't trust the server to generate
>usefule file IDs. This usually only affects remote
>NT4 NTFS and Samba < 3.0.
Running Samba 3.6.4 and it is returning
IndexNumber:
[Sigh. Resending with CC]
On May 11 11:42, starlight.201...@binnacle.cx wrote:
> Hello,
>
> Ran into a quirk that caused some trouble.
>
> For some reason CYGWIN 1.7.5 (I know this is old)
You should really update.
> is constructing inode values for files on
> Samba (3.6.4) shares with a diff
On May 11 11:42, starlight.201...@binnacle.cx wrote:
> Hello,
>
> Ran into a quirk that caused some trouble.
>
> For some reason CYGWIN 1.7.5 (I know this is old)
You should really update.
> is constructing inode values for files on
> Samba (3.6.4) shares with a different algorithm
> than is us
Hello,
Ran into a quirk that caused some trouble.
For some reason CYGWIN 1.7.5 (I know this is old)
is constructing inode values for files on
Samba (3.6.4) shares with a different algorithm
than is used for files on NTFS volumes.
This caused a script that checks for matching
hard-links to fail.
11 matches
Mail list logo
