On Feb 17, 2008 8:07 PM, Mark Shellenbaum <[EMAIL PROTECTED]> wrote:
> Rocky wrote:
> >> You most likely have some timestamps that won't fit
> >> in 32bits.
> >
> > Interesting, is that good/bad? Any work-arounds? :)
> >
>
> its not good. You shouldn't need full 64bit timestamps until 2039.
By the way, what Windows version produced those timestamps?
--
Regards,
Andrey
> I will need to have the CIFS server team investigate what validation is
> done on timestamps that are passed to ZFS.
>
> You should be able to use a 64bit ls (/usr/bin/amd64/ls) to list the files.
>
> Assuming it is a timestamp problem you can compile this little program
> to fix the affected files.
>
> #include <stdio.h>
> #include <utime.h>
>
> int
> main(int argc, char *argv[])
> {
> utime(argv[1], NULL);
> }
>
>
>
> Just compile it and the pass it the name of a file to fix.
>
> $ ./t <file>
>
> This will reset the timestamps to the current system time.
>
>
> -Mark
>
>
> >> What Windows program created those files?
> >
> > It was some Olympus camera software...
> >
> >
> > This message posted from opensolaris.org
> > _______________________________________________
> > storage-discuss mailing list
> > [email protected]
> > http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
