| To: | XFS Mailing List <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems? |
| From: | Juri Haberland <juri@xxxxxxxxxxxxxx> |
| Date: | Thu, 13 Mar 2003 23:33:19 +0100 |
| In-reply-to: | <3E7105FC.2060508@cox.net> |
| References: | <3E70E46A.20901@cox.net> <1047586257.30836.58.camel@jen.americas.sgi.com> <3E70ECD9.2080008@cox.net> <1047589045.12814.2.camel@jen.americas.sgi.com> <3E70F3AD.5090209@cox.net> <1047590194.1306.28.camel@pip> <3E70F881.7040605@cox.net> <3E710497.8030208@koschikode.com> <3E7105FC.2060508@cox.net> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 |
Kevin P. Fleming wrote: > Juri Haberland wrote: >> Maybe it's a more generic problem and related to the following bug Ted >> Ts'o just found: >> "[PATCH] BUGFIX: Ext2/3 noatime and dirsync sometimes ignored" >> http://marc.theaimsgroup.com/?l=linux-kernel&m=104754557025362&w=2 >> >> Just a(nother) shot in the dark... > I don't think so; my ext2 filesystem on the same machine works just fine. Yes, you mentioned it. And this bug is only in connection with DIRSYNC... Back to lurking ;) Juri |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems?, Kevin P. Fleming |
|---|---|
| Next by Date: | [Bug 197] stalled files in /var/lock, data fork in ino 79692177 claims free block 5040984, bugzilla-daemon |
| Previous by Thread: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems?, Kevin P. Fleming |
| Next by Thread: | TAKE - Move sector_t def to a more appropriate spot, Rusell Cattelan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |