All of lore.kernel.org
 help / color / mirror / Atom feed
From: jshankar <jshankar@CS.ColoState.EDU>
To: "Richard B. Johnson" <root@chaos.analogic.com>,
	Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: ext3 file system
Date: Wed, 17 Dec 2003 16:25:11 -0700	[thread overview]
Message-ID: <3FF18FD8@webmail.colostate.edu> (raw)

Hello,

Please provide some more insight.

Suppose a filesystem issues a write command to the disk with around 10 4K 
Blocks  to be written. SCSI device point of view i don't get what is the 
parallel I/O.
It has only 1 write command. If some other sends a write request it needs to 
be queued. But the next question arises how the write data would be handled. 
Does it mean the SCSI does not give a response for the block of data written. 
In otherwords does it mean that the response would be given after all the 
block of data is written for a single write request.
 
Thanks
Jay




>===== Original Message From Mike Fedyk <mfedyk@matchmail.com> =====
>On Wed, Dec 17, 2003 at 05:25:49PM -0500, Richard B. Johnson wrote:
>> to the physical media. There are special file-systems (journaling)
>> that guarantee that something, enough to recover the data, is
>> written at periodic intervals.
>
>Most journaling filesystems make guarantees on the filesystem meta-data, but
>not on the data.  Some like ext3, and reiserfs (with suse's journaling
>patch) can journal the data, or order things so that the data is written
>before any pointers (ie meta-data) make it to the disk so it will be harder
>to loose data.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html


             reply	other threads:[~2003-12-17 23:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 23:25 jshankar [this message]
2003-12-17 23:59 ` ext3 file system Brad Boyer
2003-12-18  1:25 ` Hans Reiser
2003-12-18 14:17 ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2003-12-18  4:47 jshankar
2003-12-18  8:39 ` Mike Fedyk
2003-12-18 10:41   ` Hans Reiser
2003-12-17 22:13 jshankar
2003-12-17 22:25 ` Richard B. Johnson
2003-12-17 23:02   ` Mike Fedyk
2002-07-20  6:13 Peter
2002-07-20 11:26 ` pa3gcu
2002-07-20 16:22 ` 1stFlight
2002-08-03 20:24 ` Benny Pedersen
2002-01-17 21:45 Justin Smith
2002-01-18 15:14 ` Noah silva
2002-01-18 15:43 ` Stephen Smalley
2002-01-18 15:53 ` Stephen Smalley
2002-01-18 17:14   ` Paul Kronenwetter

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=3FF18FD8@webmail.colostate.edu \
    --to=jshankar@cs.colostate.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=root@chaos.analogic.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.