Neil Brown wrote:
On Tuesday February 27, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
When md find a bad block (read failure) it either fixes it (by
successfully over-writing the correct date) or fails the drive.
The count of the times that this has happened is available via
/sys/blo
Currently raid456 queues up work to a single raid5d thread per array.
Since there are no dependencies between operations on different stripes
I believed a speed up could be obtained by spreading the handle_stripe
load across all available CPU's. However I am not seeing a speed up, as
measured by t
Just an update for everyone on this (and for the archives), Did some digging,
and had a look at the device mapper config
# dmsetup -C info
Name Maj Min Stat Open Targ Event UUID
mpath0 253 0 L--w11 0
VolGroup00-LogVol01 253 3 L--w11 0
LVM-2s
On 2/27/07, Gaston, Jason D <[EMAIL PROTECTED]> wrote:
Hello,
Can someone point me to where I can search a linux-raid mailing list
archive?
I use:
http://marc.theaimsgroup.com/?l=linux-raid&r=1&w=2
I am looking for information about where things are going with DMRAID
features and any discuss
> "Alan" == Alan <[EMAIL PROTECTED]> writes:
>> Not sure you're up-to-date on the T10 data integrity feature.
>> Essentially it's an extension of the 520 byte sectors common in
>> disk
[...]
Alan> but here's a minor bit of passing bad news - quite a few older
Alan> ATA controllers can't iss
Hello,
Can someone point me to where I can search a linux-raid mailing list
archive?
I am looking for information about where things are going with DMRAID
features and any discussion on where things stand in regards to the
possibility of merging MD and DMRAID. My guess, from what I have found
in
> Not sure you're up-to-date on the T10 data integrity feature.
> Essentially it's an extension of the 520 byte sectors common in disk
I saw the basics but not the detail. Thanks for the explanation it was
most helpful and promises to fix a few things for some controllers.. but
here's a minor bit
On Mon, Feb 26, 2007 at 03:40:32AM -0800, jahammonds prost wrote:
Ah ha
# ls -l /sys/block/*/holders/*
lrwxrwxrwx 1 root root 0 Feb 26 06:28 /sys/block/sdb/holders/dm-0 ->
../../../block/dm-0
lrwxrwxrwx 1 root root 0 Feb 26 06:28 /sys/block/sdc/holders/dm-0 ->
../../../block/dm-0
which I
On Tuesday February 27, [EMAIL PROTECTED] wrote:
> Neil Brown wrote:
> > When md find a bad block (read failure) it either fixes it (by
> > successfully over-writing the correct date) or fails the drive.
> >
> > The count of the times that this has happened is available via
> >/sys/block/mdX/md
On 2/26/07, Neil Brown <[EMAIL PROTECTED]> wrote:
On Monday February 26, [EMAIL PROTECTED] wrote:
> I'm pretty sure that rear errors will be noticed by the MD system,
> either.
:-) Your typing is nearly as bad as mine often is, but your intent is
correct. If you independently read from a devic
Mark Hahn wrote:
In contrast, ever since these holes appeared, drive failures became
the
norm.
wow, great conspiracy theory!
I think you misunderstand. I just meant plain old-fashioned
mis-engineering.
I should have added a smilie. but I find it dubious that the whole
industry would ha
> "Alan" == Alan <[EMAIL PROTECTED]> writes:
>> These features make the most sense in terms of WRITE. Disks
>> already have plenty of CRC on the data so if a READ fails on a
>> regular drive we already know about it.
Alan> Don't bet on it.
This is why I mentioned that I want to expose the
Stephen C Woods wrote:
As he leans on his cane, the old codger says
Well Disks used to come in open cannisters, that is you took the bottom
cover off, and then put the whould pack into the drive, and then
unscrewed the top cover and took it out.. Clearly ventilated. C 1975.
Later we g
Martin K. Petersen wrote:
"Eric" == Moore, Eric <[EMAIL PROTECTED]> writes:
Eric> Martin K. Petersen on Data Intergrity Feature, which is also
Eric> called EEDP(End to End Data Protection), which he presented some
Eric> ideas/suggestions of adding an API in linux for this.
T10 DIF is interes
On Feb 27, 2007 19:02 +, Alan wrote:
> > It would be great if the app tag was more than 16 bits. Ted mentioned
> > that ideally he'd like to store the inode number in the app tag. But
> > as it stands there isn't room.
>
> The lowest few bits are the most important with ext2/ext3 because yo
> These features make the most sense in terms of WRITE. Disks already
> have plenty of CRC on the data so if a READ fails on a regular drive
> we already know about it.
Don't bet on it. If you want to do this seriously you need an end to end
(media to host ram) checksum. We do see bizarre and qui
Neil Brown wrote:
When md find a bad block (read failure) it either fixes it (by
successfully over-writing the correct date) or fails the drive.
The count of the times that this has happened is available via
/sys/block/mdX/md/errors
What kernel provides this? I have system running everythi
> "Eric" == Moore, Eric <[EMAIL PROTECTED]> writes:
Eric> Martin K. Petersen on Data Intergrity Feature, which is also
Eric> called EEDP(End to End Data Protection), which he presented some
Eric> ideas/suggestions of adding an API in linux for this.
T10 DIF is interesting for a few things:
Tru Huynh wrote:
...
Why don't you do everything from the text/gui installation of fc6
instead of swapping distributions?
You can do everything you have said within the fc6 installer:
http://fedora.redhat.com/docs/install-guide/fc6/en/sn-disk-druid.html
boot in raid1 on sda1/sdb1
swap,/ and
On Mon, Feb 26, 2007 at 10:48:26AM -0700, Michael wrote:
> Hello,
>
...
Why don't you do everything from the text/gui installation of fc6
instead of swapping distributions?
You can do everything you have said within the fc6 installer:
http://fedora.redhat.com/docs/install-guide/fc6/en/sn-disk-d
20 matches
Mail list logo
