From tangogolfsierra77 at yahoo.com Fri Nov 6 18:23:36 2009 From: tangogolfsierra77 at yahoo.com (Terry Schima) Date: Fri, 06 Nov 2009 18:23:36 PST Subject: [ext3-discuss] Two issues with current ext2fs build for 2009.06 In-Reply-To: <4A906ABE.7080704@sun.com> Message-ID: <1299268945.601257560646840.JavaMail.Twebapp@sf-app1> Hi, I was searching for a problem that sounds like the one you are having. I also have 2009.06. And I have the two pkgs FSWfsmisc and FSWpart installed mostly to read my NTFS partitions. Everything had been working fine and I could read the NTFS partitions with no problem (I had previously not tried to read the Linux partitions because there was no need). I can still mount any of the NTFS partitions with no problem, but reading all the files is a different story. One of my NTFS partitions only allows me to read some of the files and directories. If I ls this partition (it's mounted under /mnt/e), some of the files and directories show up, but if I ls (specifically) SomeDirectoryThat_I_knowIsThere, it returns "ls cannot access SomeDirectoryThat_I_knowIsThere: I/O error". If I read the NTFS partition with Midnight Commander, all the accessible files and directories are either bright white on blue or bright green on blue (executables), but the ones I cannot access are 1. bright red on blue, 2. have a question mark as the first character in the file name and 3. have Dec. 31, 1969 as the file date. It's as if OpenSolaris and FSWfsmic are saying these files/directories are corrupt. But they read and write just fine under Windows and Linux. BTW, all the files/directories are completely accessible (as they always have been) under LinuxMint 6 (Debian > Ubuntu distro) -- sorry for the redundancy. Is this the same type of problem that you are having? I am a Unix newbie, but a DOS command line junkie, so I'm trying to learn this stuff. Anyway, if my problem is the same, at least I know it's nothing I did or am doing. If we're not having the same problem, could I have caused this problem by rebooting without first unmounting the NTFS partitions? Thanks. T -- This message posted from opensolaris.org From tangogolfsierra77 at yahoo.com Fri Nov 6 18:27:04 2009 From: tangogolfsierra77 at yahoo.com (Terry Schima) Date: Fri, 06 Nov 2009 18:27:04 PST Subject: [ext3-discuss] Two issues with current ext2fs build for 2009.06 In-Reply-To: <1299268945.601257560646840.JavaMail.Twebapp@sf-app1> Message-ID: <1801761561.611257560854924.JavaMail.Twebapp@sf-app1> I forgot to say that I had booted from the XP CD and ran chkdsk on all the NTFS partitions. Everything seemed to be hunky doree. T -- This message posted from opensolaris.org From senoltj at centrum.cz Tue Nov 10 02:32:56 2009 From: senoltj at centrum.cz (Jan Senolt) Date: Tue, 10 Nov 2009 11:32:56 +0100 Subject: [ext3-discuss] Two issues with current ext2fs build for 2009.06 In-Reply-To: <1299268945.601257560646840.JavaMail.Twebapp@sf-app1> References: <1299268945.601257560646840.JavaMail.Twebapp@sf-app1> Message-ID: <1257849176.585977.9703.nullmailer@mail1008.cent> Hi Terry, that problem in our driver was caused by overflow during inode number to block number translation. The driver then read incorrect inode (or even non-inode data) and file seemed to had strange size, date, attributes and so on. The NTFS driver probably do some similar translations but I'm not able to estimate if there is the same or similar problem, sorry:-( Try to contact author(s) of FSWfsmisc. Best regards, Jan ______________________________________________________________ > Od: "Terry Schima" > Komu: ext3-discuss at opensolaris.org > Datum: 07.11.2009 03:24 > P?edm?t: Re: [ext3-discuss] Two issues with current ext2fs build for 2009.06 > >Hi, > >I was searching for a problem that sounds like the one you are having. I also have 2009.06. And I have the two pkgs FSWfsmisc and FSWpart installed mostly to read my NTFS partitions. Everything had been working fine and I could read the NTFS partitions with no problem (I had previously not tried to read the Linux partitions because there was no need). > >I can still mount any of the NTFS partitions with no problem, but reading all the files is a different story. One of my NTFS partitions only allows me to read some of the files and directories. If I ls this partition (it's mounted under /mnt/e), some of the files and directories show up, but if I ls (specifically) SomeDirectoryThat_I_knowIsThere, it returns > >"ls cannot access SomeDirectoryThat_I_knowIsThere: I/O error". > >If I read the NTFS partition with Midnight Commander, all the accessible files and directories are either bright white on blue or bright green on blue (executables), but the ones I cannot access are 1. bright red on blue, 2. have a question mark as the first character in the file name and 3. have Dec. 31, 1969 as the file date. It's as if OpenSolaris and FSWfsmic are saying these files/directories are corrupt. But they read and write just fine under Windows and Linux. > >BTW, all the files/directories are completely accessible (as they always have been) under LinuxMint 6 (Debian > Ubuntu distro) -- sorry for the redundancy. > >Is this the same type of problem that you are having? I am a Unix newbie, but a DOS command line junkie, so I'm trying to learn this stuff. Anyway, if my problem is the same, at least I know it's nothing I did or am doing. > >If we're not having the same problem, could I have caused this problem by rebooting without first unmounting the NTFS partitions? Thanks. > >T >-- >This message posted from opensolaris.org >_______________________________________________ >ext3-discuss mailing list >ext3-discuss at opensolaris.org >http://mail.opensolaris.org/mailman/listinfo/ext3-discuss > From senoltj at opensolaris.org Wed Nov 11 13:09:35 2009 From: senoltj at opensolaris.org (senoltj at opensolaris.org) Date: Wed, 11 Nov 2009 13:09:35 -0800 (PST) Subject: [ext3-discuss] 0000016: rename failed Message-ID: <200911112109.nABL9Zoi006188@sf-app2.opensolaris.org> Author: senoltj at opensolaris.org Repository: /hg/ext3/ext2-gate Latest revision: 8c8ea7e8594eec84bcdd75a8bcd6d4cac2457423 Total changesets: 1 Log message: 0000016: rename failed Files: update: usr/src/uts/common/fs/ext2fs/ext2_alloc.c update: usr/src/uts/common/fs/ext2fs/ext2_dir.c update: usr/src/uts/common/fs/ext2fs/ext2_inode.c update: usr/src/uts/common/fs/ext2fs/ext2_subr.c update: usr/src/uts/common/fs/ext2fs/ext2_vfsops.c update: usr/src/uts/common/fs/ext2fs/ext2_vnops.c update: usr/src/uts/common/sys/fs/ext2_dir.h From senoltj at centrum.cz Thu Nov 12 02:28:01 2009 From: senoltj at centrum.cz (Jan Senolt) Date: Thu, 12 Nov 2009 11:28:01 +0100 Subject: [ext3-discuss] 0000013: sticky bit Message-ID: <1258021681.596001.25504.nullmailer@mail1004.cent> Hi, I added a support for sticky bit to ext2_dirremove(). There is a new function ext2_sticky_remove_access() used by ext2_dirremove() to check sticky bit and eventually ownership of file and/or directory. Webrev is available here: http://cr.opensolaris.org/~senoltj/0000013_rmdir_and_sticky_bit_1 Could somebody review my bug fix of issue 0000013 before put-back, please? Best regards, Jan From senoltj at opensolaris.org Mon Nov 16 08:55:15 2009 From: senoltj at opensolaris.org (senoltj at opensolaris.org) Date: Mon, 16 Nov 2009 08:55:15 -0800 (PST) Subject: [ext3-discuss] 0000016_rename_failed_002: ext2_dirremove() and ext2_diraddname() etc were rewritten. Message-ID: <200911161655.nAGGtF6e008771@sf-app2.opensolaris.org> Author: senoltj at opensolaris.org Repository: /hg/ext3/ext2-gate Latest revision: 543743e17b3d3efe290c071f14b76eb8722cba3a Total changesets: 1 Log message: 0000016_rename_failed_002: ext2_dirremove() and ext2_diraddname() etc were rewritten. Files: update: usr/src/uts/common/fs/ext2fs/ext2_alloc.c update: usr/src/uts/common/fs/ext2fs/ext2_dir.c update: usr/src/uts/common/fs/ext2fs/ext2_inode.c update: usr/src/uts/common/fs/ext2fs/ext2_subr.c update: usr/src/uts/common/fs/ext2fs/ext2_vfsops.c update: usr/src/uts/common/fs/ext2fs/ext2_vnops.c update: usr/src/uts/common/sys/fs/ext2_dir.h From senoltj at opensolaris.org Mon Nov 16 08:55:17 2009 From: senoltj at opensolaris.org (senoltj at opensolaris.org) Date: Mon, 16 Nov 2009 08:55:17 -0800 (PST) Subject: [ext3-discuss] new function ext2_sticky_remove_access() Message-ID: <200911161655.nAGGtHKX009036@sf-app2.opensolaris.org> Author: senoltj at opensolaris.org Repository: /hg/ext3/ext2-gate Latest revision: c1ef223b14bbe0ecad83208136e6e5eda9ef876f Total changesets: 1 Log message: new function ext2_sticky_remove_access() Files: update: usr/src/uts/common/fs/ext2fs/ext2_dir.c From senoltj at opensolaris.org Mon Nov 16 08:55:16 2009 From: senoltj at opensolaris.org (senoltj at opensolaris.org) Date: Mon, 16 Nov 2009 08:55:16 -0800 (PST) Subject: [ext3-discuss] 0000013: do not rmdir when user does not own the sticky dir nor the dir to be removed Message-ID: <200911161655.nAGGtGJ1008919@sf-app2.opensolaris.org> Author: senoltj at opensolaris.org Repository: /hg/ext3/ext2-gate Latest revision: 78f8a5698869f12cb2de415ce42a20de020d6486 Total changesets: 1 Log message: 0000013: do not rmdir when user does not own the sticky dir nor the dir to be removed Files: update: usr/src/uts/common/fs/ext2fs/ext2_dir.c From senoltj at opensolaris.org Mon Nov 16 08:55:18 2009 From: senoltj at opensolaris.org (senoltj at opensolaris.org) Date: Mon, 16 Nov 2009 08:55:18 -0800 (PST) Subject: [ext3-discuss] 0000013: do not rmdir when user does not own the sticky dir nor the dir to be removed Message-ID: <200911161655.nAGGtISr009155@sf-app2.opensolaris.org> Author: senoltj at opensolaris.org Repository: /hg/ext3/ext2-gate Latest revision: fc40a1b9abe870f796f9653e1d7624f7f3b7b7cd Total changesets: 1 Log message: 0000013: do not rmdir when user does not own the sticky dir nor the dir to be removed Files: update: usr/src/uts/common/fs/ext2fs/ext2_dir.c update: usr/src/uts/common/fs/ext2fs/ext2_vnops.c update: usr/src/uts/common/sys/fs/ext2_dir.h update: usr/src/uts/common/sys/fs/ext2_inode.h From senoltj at centrum.cz Thu Nov 19 05:05:21 2009 From: senoltj at centrum.cz (Jan Senolt) Date: Thu, 19 Nov 2009 14:05:21 +0100 Subject: [ext3-discuss] 0000010: open(2) should update mtime and ctime Message-ID: <1258635921.517551.3139.nullmailer@mail1002.cent> Hi, here http://cr.opensolaris.org/~senoltj/0000010_open_should_update_mtime_and_ctime_1/ is available webrev with bug-fix for issue 0000010. Short explanation of bug and bug-fix is in mantis. Could somebody review my code before put-back, please? Best regards, Jan