linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Sun, 12 Apr 2009 12:43:06 -0400	[thread overview]
Message-ID: <49E21A1A.4020004@hp.com> (raw)
In-Reply-To: <49E1CC6F.7020409@garzik.org>

To continue the pointless (but maybe entertaining) argument :)

Jeff Garzik wrote:
> jim owens wrote:
>> The filesystem mod-time might have nanoseconds in it, but
>> that does not mean 2 writes 100 nanoseconds apart will have
>> different mod-times.
> 
> Modern Linux filesystems absolutely do do metadata updates at that level 
> of granularity.

In filesystems it only counts if it makes it to disk.

10,000,000 write-to-disk metadata updates per second?  I think not.

Even the top-of-the-line intel ssd can only do 3,300 writes per second.

> Are you guaranteed district timestamps between writes?  No, but then 
> again, metadata updates were never guaranteed between two writes either. 
>  You might just be dirtying a mmap'd page, for example.

So this sounds like you at least agree with my original statement
that mod-time is not a 100% guarantee that no write occurred after
you read a particular block of a file.  Regardless of the fact we
disagree about how accurate filesystems record times.

jim

  reply	other threads:[~2009-04-12 16:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10  9:10 ` KwangErn Liew
2009-04-10  9:55   ` CoolCold
2009-04-10 19:43     ` Timothy D. Lenz
2009-04-10 19:53   ` Robin Hill
2009-04-10 20:45     ` Timothy D. Lenz
2009-04-10 20:59       ` Robin Hill
2009-04-10 21:26         ` Timothy D. Lenz
2009-04-10 21:51           ` Robin Hill
2009-04-11  5:29             ` Timothy D. Lenz
2009-04-11 14:29               ` CoolCold
2009-04-11 18:47                 ` Timothy D. Lenz
2009-04-12  0:53                   ` Timothy D. Lenz
2009-04-12 11:11                     ` Robin Hill
2009-04-12 19:55                       ` Timothy D. Lenz
2009-04-14  9:30                         ` Robin Hill
2009-04-17  0:47                           ` Timothy D. Lenz
2009-04-17  7:49                             ` Robin Hill
2009-04-11 14:36               ` Robin Hill
2009-04-11 15:04                 ` jim owens
2009-04-11 15:44                   ` Jeff Garzik
2009-04-11 17:40                     ` jim owens
2009-04-12 11:11                       ` Jeff Garzik
2009-04-12 16:43                         ` jim owens [this message]
2009-04-12 17:18                           ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22   ` Timothy D. Lenz
2009-04-10 19:50     ` Robin Hill
2009-04-11  4:40       ` Jon Lewis
2009-04-11  7:48         ` Jan Ceuleers
2009-04-11  8:50         ` Goswin von Brederlow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49E21A1A.4020004@hp.com \
    --to=jowens@hp.com \
    --cc=jeff@garzik.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).