All of lore.kernel.org
 help / color / mirror / Atom feed
From: jshankar <jshankar@CS.ColoState.EDU>
To: linux-raid@vger.kernel.org
Cc: jshankar@CS.ColoState.EDU
Subject: raid question
Date: Sun, 17 Aug 2003 17:19:14 -0600	[thread overview]
Message-ID: <3F405F90@webmail.colostate.edu> (raw)

Hello,

I have couple of questions regarding raid routine.

1> When i do mkraid, is there any specific routines in md.c that is 
responsible for adding and tracking the device. I have maintain the entries in 
/etc/raidtab. When i copy a file into the raid device, is there any specific 
routine that track  the  device to write the next block( raid 0  case).

2> Also the routine that  keeps track the amount
of buffer size that can be written to each particular device and the case when
the writing to one disk fails.



3> Also i was  wondering whether the source code of raid tools are availaible 
in
linux directory.

It would be great if somebody  can throw some light.

Thanks in advance.


-Jay



>===== Original Message From Neil Brown <neilb@cse.unsw.edu.au> =====
>On Wednesday July 30, jshankar@CS.ColoState.EDU wrote:
>> Hello ,
>>
>> I am Jayshankar, Masters student in Colorado State UNiversity.
>>
>> A small question on raid.
>>
>> Suppose i have got raid0 connected to disk1, disk2 , disk3 , disk4.
>>
>> The operating system writes a block of data to disk1 then to disk2, disk3,
>> disk4. Do the I/O needs to be successful on disk1, for writing the next
block
>> of data on disk2, disk3, disk4. Or it checks the I/O is successful on
disk1,
>> after the block of data has been written to disk2,disk3,disk4.
>>
>>
>> Looking forward for your reply.
>>
>> THanks in advance.
>>
>> -Jay
>
>Please send future questions to
>  linux-raid@vger.kernel.org
>rather than to me personally.
>
>All disk IO in Linux is asynchronous.
>i.e. submitting a block schedules it for IO.  If you submit lots of
>blocks they all get scheduled for IO.  This is true whether your are
>accessing a single device or a raid array.
>
>So there is no check for success of one block before writing the
>next.  quite often the blocks writen to the different drive will all
>be written at one.
>
>NeilBrown


             reply	other threads:[~2003-08-17 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 23:19 jshankar [this message]
2003-08-20  6:31 ` raid question Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2001-11-07 15:22 RAID question Bene, Martin
2001-11-07 22:09 ` Lionel Bouton
2001-11-07 14:55 Roy Sigurd Karlsbakk
2001-05-03 21:38 OT: Here's the article text -- Microsoft Is Set to Be Top Foe of Free Code Miles Lane
2001-05-08  2:48 ` RAID question Peter Waltenberg
2001-05-08 15:07   ` Jakob Østergaard

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=3F405F90@webmail.colostate.edu \
    --to=jshankar@cs.colostate.edu \
    --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 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.