*** introductory notes *** the following bugs are tested with solaris, opensolaris, linux and windows, on an manually mounted internal FAT32 disk and an automatically mounted external FAT32 key; solaris is "SunOS solaris-devx 5.11 snv_70b i86pc i386 i86pc", opensolaris is "SunOS opensolaris 5.11 snv_75 i86pc i386 i86pc Solaris", linux is "Ubuntu 7.10", windows is "Windows XP SP2".
*** first bug: LAST MODIFICATION DATE/TIME AND CASE WRONGLY SHOWN ON FILE READ *** description: - on solaris a lowcase file is shown as upcase + the date is incremented of 1 day - on opensolaris a lowcase file is shown as upcase + the date is incremented of 1 day and 1 hour listing the same directory on linux, windows, solaris and opensolaris: ### linux: date ok, time ok, case ok total 12 drwx------ 2 ste root 4096 2008-01-05 15:29 . drwx------ 7 ste root 4096 2008-01-05 16:38 .. -rwx------ 1 ste root 3399 2008-01-03 17:45 solaris ### windows: date ok, time ok, case ok 05/01/2008 11.29 <DIR> . 05/01/2008 11.29 <DIR> .. 03/01/2008 17.45 3.399 solaris ### solaris: date wrong, time ok, case wrong total 23 drwxrwxrwx 1 ste staff 4096 Jan 6 14:45:50 2008 . drwxrwxrwx 1 ste staff 4096 Jan 2 00:00:00 1980 .. -rwxrwxrwx 1 ste staff 3399 Jan 4 17:45:36 2008 SOLARIS ### opensolaris: date wrong, time wrong, case wrong total 12 drwxrwxrwx 1 ste staff 4096 Jan 6 2008 . drwxrwxrwx 1 ste staff 4096 Jan 5 16:11 .. -rwxrwxrwx 1 ste staff 3399 Jan 4 18:45 SOLARIS *** second bug: A FILE CREATED IN DAY 'N' HAS MODIFY DAY 'N+1' AND IF COPIED WITH RSYNC HAS MODIFY DATE 'N+2' *** description: - a file created today is written with date tomorrow; copying the same file with "rsync --times" some seconds after the creation the date of the copied file is incremented of 2 days from today the script I used to test the bug with rsync: ### script to be executed on a FAT32 formatted disk. ### the sleep is needed to let the bug manifest himself ### ### note that the current date is 2007-1-5, the file is created with date ### 2007-1-6 and rsync copied with date 2007-1-7 # date Sat Jan 5 15:21:31 CET 2008 [ ! -d testdir ] && mkdir testdir [ ! -d testdir.bak ] && mkdir testdir.bak # echo xyz > testdir/testfile # stat testdir/testfile File: `testdir/testfile' Size: 4 Blocks: 1 IO Block: 4096 regular file Device: 1981010h/26742800d Inode: 1711135027 Links: 1 Access: (0777/-rwxrwxrwx) Uid: ( 101/ ste) Gid: ( 10/ staff) Access: 2008-01-06 15:21:30.000000000 +0100 Modify: 2008-01-06 15:21:30.000000000 +0100 Change: 2008-01-06 15:21:30.000000000 +0100 # sleep 2 # rsync --times testdir/* testdir.bak/ # stat testdir.bak/testfile File: `testdir.bak/testfile' Size: 4 Blocks: 1 IO Block: 4096 regular file Device: 1981010h/26742800d Inode: 1711135157 Links: 1 Access: (0777/-rwxrwxrwx) Uid: ( 101/ ste) Gid: ( 10/ staff) Access: 2008-01-06 01:00:00.000000000 +0100 Modify: 2008-01-07 15:21:30.000000000 +0100 Change: 2008-01-07 15:21:30.000000000 +0100 *** third bug: I/O ERROR ON A GOOD FILE *** a file, correctly read (with md5sum) by linux and windows shows the following error on solaris and opensolaris: # md5sum /media/lap0-iop/mydocuments/it.repo/office/ooo/docs/0200WG-WriterGuide.pdf md5sum: /media/lap0-iop/mydocuments/it.repo/office/ooo/docs/0200WG-WriterGuide.pdf: I/O error *** final notes *** I'm a former fulltime linux user, willing to use linux as a desktop and solaris as my file server. Please let me know if I can do something to help further with those bugs... bye --- Stefano Spinucci This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
