Skip to contentSkip to conversation

bio too big device

DISCUSSION scott thomason 9 participants 33 messages Mar 12, 2003 – Mar 14, 2003

lore
Share & tools
lore
#0 lore raw

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)

It's worth noting that on this system I have had ongoing trouble with system stability during write activity as well, using a wide variety of 2.5.x kernels, even though at the time of this symptom things are apparently running fine.

Filesystems are all ext3 on top soft raid0 devices. This happens to be 2.5.64, but it has been happening for at least the last 5-6 versions.

Ideas? Any further debugging output I can provide? ---scott

#1 lore raw

After a little more digging in drivers/block/ll_rw_blk.c, it seems that Jens might be the best person to discuss the following with.

Apparently I have a system that is making bio requests of a size that exceeds the max sector size for the device? How is that possible, and more to the point, how can I help get it fixed?

Or am I misinterpreting something?
---scott

Quoted 24 lines · scott thomason

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)

It's worth noting that on this system I have had ongoing trouble with system stability during write activity as well, using a wide variety of 2.5.x kernels, even though at the time of this symptom things are apparently running fine.

Filesystems are all ext3 on top soft raid0 devices. This happens to be 2.5.64, but it has been happening for at least the last 5-6 versions.

Ideas? Any further debugging output I can provide? ---scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at
http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
Quoted 9 lines · scott thomason

After a little more digging in drivers/block/ll_rw_blk.c, it seems that Jens might be the best person to discuss the following with.

Apparently I have a system that is making bio requests of a size that exceeds the max sector size for the device? How is that possible, and more to the point, how can I help get it fixed?

Or am I misinterpreting something?

Search the lkml archives, this has been answered before in more detail. In short, it's a raid bug.

Signature · 1 line
Jens Axboe
#3 lore raw
In reply to scott thomason
Quoted 11 lines · On Tuesday March 11, [email protected] wrote:

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)

It's worth noting that on this system I have had ongoing trouble with system stability during write activity as well, using a wide variety of 2.5.x kernels, even though at the time of this symptom things are apparently running fine.

Quoted 5 lines

Filesystems are all ext3 on top soft raid0 devices. This happens to be 2.5.64, but it has been happening for at least the last 5-6 versions.

Ideas? Any further debugging output I can provide?

raid0 doesn't really work well in 2.5 yet.... as you have noticed.

We really need to grab the bio splitting code out of md/dm.c and use it to split bios that are too big or that cross device boundaries.

any volunteers??

NeilBrown

#4 lore raw
Quoted 10 lines · you

raid0 doesn't really work well in 2.5 yet.... as you have noticed.

We really need to grab the bio splitting code out of md/dm.c and use it to split bios that are too big or that cross device boundaries.

any volunteers??

NeilBrown

Given all the grief I've encountered with ALSA, SCSI emulation, other stuff, and now RAID 0, I would certainly say that the spelling corrections may have been a little premature. It doesn't feel ready for 2.6 to me :(
---scott

#5 lore raw
In reply to Neil Brown
Quoted 19 lines · Neil Brown
Quoted 11 lines · On Tuesday March 11, [email protected] wrote:

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)

It's worth noting that on this system I have had ongoing trouble with system stability during write activity as well, using a wide variety of 2.5.x kernels, even though at the time of this symptom things are apparently running fine.

Quoted 5 lines

Filesystems are all ext3 on top soft raid0 devices. This happens to be 2.5.64, but it has been happening for at least the last 5-6 versions.

Ideas? Any further debugging output I can provide?

Quoted 6 lines

raid0 doesn't really work well in 2.5 yet.... as you have noticed.

We really need to grab the bio splitting code out of md/dm.c and use it to split bios that are too big or that cross device boundaries.

any volunteers??

I can give it a shot

Signature · 1 line
Jens Axboe
#6 lore raw
In reply to scott thomason

That has to be a BIO bug or IDE setup bug.

256 sectors is legal and correct for 28-bit addressing.

Cheers,

Quoted 15 lines · scott thomason

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)

It's worth noting that on this system I have had ongoing trouble with system stability during write activity as well, using a wide variety of 2.5.x kernels, even though at the time of this symptom things are apparently running fine.

Filesystems are all ext3 on top soft raid0 devices. This happens to be 2.5.64, but it has been happening for at least the last 5-6 versions.

Quoted 8 lines

Ideas? Any further debugging output I can provide?
---scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Andre Hedrick
LAD Storage Consulting Group

#7 lore raw
Quoted 7 lines · scott thomason
Quoted 6 lines

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)
Quoted 3 lines · Andre Hedrick

That has to be a BIO bug or IDE setup bug.

256 sectors is legal and correct for 28-bit addressing.

Yes, it is. However, Paul Gortmaker reported on his old 700MB Maxtor 7850 AV that would give errors with 256-sector requests and work well with 255-sector requests. In a later post he added that one has to work hard to evoke this error - usually 256-sector requests are fine, but after torturing the disk with an hour of simultaneous untar and make, an error occurred.

Maybe that is the only disk that gives problems.

Jens replied:

= The 256 is _not_ a bug in the driver, it's more likely a bug in your = drive. 256 is a perfectly legal transfer size. That said, maybe it is = a good idea to leave it at 255 just for safety

So that is how this length was limited.

In short: 256 is legal, has always been legal, nothing wrong with it. But at least one old disk has been discovered that was happier with 255.

Andries

#8 lore raw

Well that is the first complete explaination of the 255 limit. That belongs in a simple dirty drive list in ide-probe.c (or whatever the latest filename is) and then dump this issue for good.

Cheer,

Quoted 29 lines · Andries Brouwer
Quoted 7 lines · scott thomason
Quoted 6 lines

I frequently receive this message in my syslog, apparently whenever there are periods of significant write activity:

    bio too big device ide0(3,7) (256 > 255)
    bio too big device ide1(22,6) (256 > 255)
Quoted 3 lines · Andre Hedrick

That has to be a BIO bug or IDE setup bug.

256 sectors is legal and correct for 28-bit addressing.

Yes, it is. However, Paul Gortmaker reported on his old 700MB Maxtor 7850 AV that would give errors with 256-sector requests and work well with 255-sector requests. In a later post he added that one has to work hard to evoke this error - usually 256-sector requests are fine, but after torturing the disk with an hour of simultaneous untar and make, an error occurred.

Maybe that is the only disk that gives problems.

Jens replied:

= The 256 is _not_ a bug in the driver, it's more likely a bug in your = drive. 256 is a perfectly legal transfer size. That said, maybe it is = a good idea to leave it at 255 just for safety

Quoted 7 lines

So that is how this length was limited.

In short: 256 is legal, has always been legal, nothing wrong with it. But at least one old disk has been discovered that was happier with 255.

Andries

Andre Hedrick
LAD Storage Consulting Group

#9 lore raw
In reply to Andre Hedrick
Quoted 2 lines · Andre Hedrick

That has to be a BIO bug or IDE setup bug.

raid bug

Quoted 1 line

256 sectors is legal and correct for 28-bit addressing.

yes, but ide itself limits incoming requests to 255 sectors. so it cannot get 256 sector requests.

Signature · 1 line
Jens Axboe
#10 lore raw

So lets dirty list the one drive by Paul G. and be done. Can we do that?

Cheers,

Quoted 14 lines · Jens Axboe
Quoted 2 lines · Andre Hedrick

That has to be a BIO bug or IDE setup bug.

raid bug

Quoted 1 line

256 sectors is legal and correct for 28-bit addressing.

yes, but ide itself limits incoming requests to 255 sectors. so it cannot get 256 sector requests.

Signature · 1 line
Jens Axboe

Andre Hedrick
LAD Storage Consulting Group

#11 lore raw
Quoted 3 lines · Andre Hedrick

So lets dirty list the one drive by Paul G. and be done. Can we do that?

Who cares, really? There's not much point in doing it, we're talking 248 vs 256 sectors in reality. I think it's a _bad_ idea, lets just keep it at 255 and avoid silly drive bugs there.

Signature · 1 line
Jens Axboe
#12 lore raw

No that is wrong to force all other drives to under perform because on one. If you are going to impose 255 then pushi it back to 128 were it is a single scatter list. This issue has bugged me for years and now that we know the exact model we apply an exception rule to it.

This is one silly bug that I have heard about.

Cheers,

Quoted 12 lines · Jens Axboe
Quoted 3 lines · Andre Hedrick

So lets dirty list the one drive by Paul G. and be done. Can we do that?

Who cares, really? There's not much point in doing it, we're talking 248 vs 256 sectors in reality. I think it's a _bad_ idea, lets just keep it at 255 and avoid silly drive bugs there.

Signature · 1 line
Jens Axboe

Andre Hedrick
LAD Storage Consulting Group

#13 lore raw
Quoted 7 lines · Andre Hedrick

No that is wrong to force all other drives to under perform because on one. If you are going to impose 255 then pushi it back to 128 were it is a single scatter list. This issue has bugged me for years and now that we know the exact model we apply an exception rule to it.

This is one silly bug that I have heard about.

See that's the whole point, is there any performance issue with 248 vs 256 sectors? For a 248 sectors vs 256 command alone, I doubt it. The only problem I see is for potential chop-ups of 248 - 8 - 248 - 8 - 248
- 8 - etc. But due to merging, only the last command should be smaller.

So I still think it's much better stick with the safe choice. Why do you think it's only one drive that has this bug? It basically boils down to whether That Other OS uses 256 sector commands or not. If it doesn't, I wouldn't trust the drives one bit.

And finally, _I'm_ not imposing anything. The limit is driver tweakable, always has been.

Signature · 1 line
Jens Axboe
#14 lore raw
Quoted 4 lines · Jens Axboe

So I still think it's much better stick with the safe choice. Why do you think it's only one drive that has this bug? It basically boils down to whether That Other OS uses 256 sector commands or not. If it doesn't, I wouldn't trust the drives one bit.

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

Andries

#15 lore raw
Quoted 10 lines · Andries Brouwer
Quoted 4 lines · Jens Axboe

So I still think it's much better stick with the safe choice. Why do you think it's only one drive that has this bug? It basically boils down to whether That Other OS uses 256 sector commands or not. If it doesn't, I wouldn't trust the drives one bit.

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

Have you read the thread? You are obviously mistaken.

Signature · 1 line
Jens Axboe
#16 lore raw
Quoted 8 lines · Jens Axboe
Quoted 7 lines · Andries Brouwer
Quoted 4 lines · Jens Axboe

So I still think it's much better stick with the safe choice. Why do you think it's only one drive that has this bug? It basically boils down to whether That Other OS uses 256 sector commands or not. If it doesn't, I wouldn't trust the drives one bit.

Quoted 5 lines
Quoted 3 lines

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

Have you read the thread? You are obviously mistaken.

Usually I am not, but I am happy to be corrected.
Please point out the facts.

What I have seen is Paul Gortmaker, who reported on an old disk that showed errors with 256 sector transfers. In an early post he thought that that just was because the drive did not understand 256-sector transfers, in a later post he reported that in fact 256-sector transfers worked but that it was possible to provoke a problem by having heavy load for an hour with 256-sector transfers.

I have an old drive that works fine but after three crashes at 4 in the morning I decided that the load of updating the locate database was more than it could handle. Heavy load is something that kills many a machine.

Andries

#17 lore raw
Quoted 26 lines · Andries Brouwer
Quoted 8 lines · Jens Axboe
Quoted 7 lines · Andries Brouwer
Quoted 4 lines · Jens Axboe

So I still think it's much better stick with the safe choice. Why do you think it's only one drive that has this bug? It basically boils down to whether That Other OS uses 256 sector commands or not. If it doesn't, I wouldn't trust the drives one bit.

Quoted 5 lines
Quoted 3 lines

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

Have you read the thread? You are obviously mistaken.

Usually I am not, but I am happy to be corrected.
Please point out the facts.

What I have seen is Paul Gortmaker, who reported on an old disk that showed errors with 256 sector transfers. In an early post he thought that that just was because the drive did not understand 256-sector transfers, in a later post he reported that in fact 256-sector transfers worked but that it was possible to provoke a problem by having heavy load for an hour with 256-sector transfers.

Quoted 4 lines

I have an old drive that works fine but after three crashes at 4 in the morning I decided that the load of updating the locate database was more than it could handle. Heavy load is something that kills many a machine.

Either the drive has the bug or not. I seriously doubt that 256 vs 248 sectors would put any extra strain on the drive.

If there's no real precedent wrt 256 sector bug in _any_ drive, then I'm fine with that change. Remember that we _did_ have it that way for a while, it was only changed back because of apparent problems. If those problems turn out to be non-existant, then the error was changing it away from 256 in the first place.

Signature · 1 line
Jens Axboe
#18 lore raw
In reply to Jens Axboe
Quoted 5 lines
Quoted 3 lines

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

Have you read the thread? You are obviously mistaken.

I've read most of it, and as far as I can see the problem is that one drive is known to accept 256 sector commands and occasionally fail on them. Since that is obviously broken behavior, I don't see how it can possibly even be suggested that we reduce the performance of possibly every other hard disk in use[1] just to compensate for it.

[1] Note that the known broken disk is 700 MB one, so there probably aren't many in use anyway.

John.

#19 lore raw
In reply to Andries Brouwer

In article <[email protected]>,

Quoted 10 lines · Andries Brouwer
Quoted 4 lines · Jens Axboe

So I still think it's much better stick with the safe choice. Why do you think it's only one drive that has this bug? It basically boils down to whether That Other OS uses 256 sector commands or not. If it doesn't, I wouldn't trust the drives one bit.

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

That is definitely not true. We definitely _have_ had drives that misconstrue the 256-sector case. It's been a long time, but they definitely exist.

The right limit for IDE is 255 sectors, and doing 256 sectors WILL fail on some setups.

Linus

#20 lore raw
Quoted 10 lines
Quoted 3 lines

I am not quite sure I understand your reasoning.
We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

That is definitely not true. We definitely _have_ had drives that misconstrue the 256-sector case. It's been a long time, but they definitely exist.

The right limit for IDE is 255 sectors, and doing 256 sectors WILL fail on some setups.

Couldn't we have a list of known good drives, though, and enable 256 sectors as a special case?

John.

#21 lore raw
Quoted 3 lines · John Bradford

Couldn't we have a list of known good drives, though, and enable 256 sectors as a special case?

My problem is that I just don't see the point. What's the difference between 256 and 254 sectors? 128kB vs 127kB?

Also, looking closer, the current limit actually seems to be _controller_ dependent, not disk-dependent. I don't know how valid that is, but it looks reasonable at least in theory - while the IDE controller is mostly a passthrough thing, it does end up doing part of the work. So the picture look smore complex than just another drive blacklist.

In short, the headaches just aren't worth the 127->128kB gain.

Linus

#22 lore raw
Quoted 5 lines
Quoted 2 lines

Couldn't we have a list of known good drives, though, and enable 256 sectors as a special case?

My problem is that I just don't see the point. What's the difference between 256 and 254 sectors? 128kB vs 127kB?

Ah, I thought there was a reason that it was a Good Thing to keep it as a power of 2, which would mean 64kB vs 128kB, but if not then I totally agree.

Quoted 7 lines

Also, looking closer, the current limit actually seems to be _controller_ dependent, not disk-dependent. I don't know how valid that is, but it looks reasonable at least in theory - while the IDE controller is mostly a passthrough thing, it does end up doing part of the work. So the picture look smore complex than just another drive blacklist.

In short, the headaches just aren't worth the 127->128kB gain.

I wasn't aware of the controller issue - with that thrown in to the mix, I see your point.

John.

#23 lore raw
In reply to Linus Torvalds
Quoted 6 lines · Linus Torvalds

That is definitely not true. We definitely _have_ had drives that misconstrue the 256-sector case. It's been a long time, but they definitely exist.

The right limit for IDE is 255 sectors, and doing 256 sectors WILL fail on some setups.

One single possible but unclear case. I'm waiting to find out what Win2K does.

We have had controllers that misconstrue it as the only definitive case and that is correctly handled by the IDE code already, which splits the DMA descriptor.

Alan

#24 lore raw
In reply to Linus Torvalds
Quoted 6 lines · Linus Torvalds
Quoted 2 lines

We have seen *zero* drives that do not understand 256 sector commands. Maybe such drives exist, but so far there is zero evidence.

That is definitely not true. We definitely _have_ had drives that misconstrue the 256-sector case. It's been a long time, but they definitely exist.

I disagree. If you have any proof, please show it.

Let me repeat:
We have seen *zero* drives that do not understand 256 sector commands.

We have seen *one* drive (a six years old Maxtor 7850AV) that could not sustain heavy load with max # secs set to 256, while it behaved better with max set to 255.

But we have seen lots of old old drives that show all kinds of errors.

Quoted 2 lines

The right limit for IDE is 255 sectors, and doing 256 sectors WILL fail on some setups.

Paul remarked: "So the 255 (or even the old 128) fixes things vs. 256, but I'd feel better being 100% sure why. Is 255 a "fix" or a perturbation that happens to paper over something else?"

I think there is no good reason to limit us to 255 sectors.

(And no reason for blacklists either - there is just no good evidence that something is systematically wrong with 256 sectors for any brand or model. Things would change if a second Maxtor 7850AV owner could confirm.)

Andries

#25 lore raw
Quoted 3 lines · Andries Brouwer

We have seen *one* drive (a six years old Maxtor 7850AV) that could not sustain heavy load with max # secs set to 256, while it behaved better with max set to 255.

[...]

Quoted 3 lines

Paul remarked: "So the 255 (or even the old 128) fixes things vs. 256, but I'd feel better being 100% sure why. Is 255 a "fix" or a perturbation that happens to paper over something else?"

As luck would have it, I kept that drive around, thinking it might be interesting to have around if the above "why" part got revisited someday.

Quoted 5 lines

I think there is no good reason to limit us to 255 sectors.

(And no reason for blacklists either - there is just no good evidence that something is systematically wrong with 256 sectors for any brand or model. Things would change if a second Maxtor 7850AV owner could confirm.)

Perhaps I can also act as the second owner in this case. :-) The drive is currently in an old 16MB P133 on a PIIX3, so after tripping over this thread, I did some testing to 1st see if I could still re-create any problems in this different box. Of note, 2.4.21pre5 reports:

hda: 1667232 sectors (854 MB) w/64KiB Cache, CHS=1654/16/63, BUG DMA OFF

                                        -------------------->^^^

which I haven't looked into yet. Anyway, I tweaked pre5 to re-allow 256 and then let it do two 2.5.64 compiles at the same time (in 16MB, this takes a while) and nothing broke. Thinking that the original problem was in an even older VLB box, I disabled DMA and did the same test. Still no breakage.

What does this mean? I'm not sure :) Maybe this simple test isn't as
harsh as the prior one from several years ago. Realistically, there
are a fair number of changes that also may have a role: e.g. ide driver, gcc, gas, kernel, CPU, mainboard, ide controller, PSU, cables, and so on all have changed. It looks like I would need to jump back into the past and test on the exact same system and then progressively rule out some of these variables.

Paul.

#26 lore raw
In reply to Andre Hedrick

Just so everyone knows...these aren't ancient drives I'm talking about. One is a 30GB Maxtor 5T030H3, less than two years old IIRC, and the other is a 30GB IBM-DTLA-307030 purchased about six months ago.
---scott

Quoted 25 lines · Andre Hedrick

No that is wrong to force all other drives to under perform because on one. If you are going to impose 255 then pushi it back to 128 were it is a single scatter list. This issue has bugged me for years and now that we know the exact model we apply an exception rule to it.

This is one silly bug that I have heard about.

Cheers,

Quoted 11 lines · Jens Axboe
Quoted 2 lines · Andre Hedrick

So lets dirty list the one drive by Paul G. and be done. Can we do that?

Who cares, really? There's not much point in doing it, we're talking 248 vs 256 sectors in reality. I think it's a _bad_ idea, lets just keep it at 255 and avoid silly drive bugs there.

--
Jens Axboe

Andre Hedrick
LAD Storage Consulting Group

#27 lore raw
Quoted 4 lines · scott thomason

Just so everyone knows...these aren't ancient drives I'm talking about. One is a 30GB Maxtor 5T030H3, less than two years old IIRC, and the other is a 30GB IBM-DTLA-307030 purchased about six months ago.

What Andre and I are talking about know is an entirely different issue, not related to your problem at all.

Signature · 1 line
Jens Axboe
#28 lore raw
In reply to scott thomason
Quoted 4 lines · scott thomason

Just so everyone knows...these aren't ancient drives I'm talking about. One is a 30GB Maxtor 5T030H3, less than two years old IIRC, and the other is a 30GB IBM-DTLA-307030 purchased about six months ago.

The conversation drifted ontoa different issue, your drives are fine, in your case you are hitting bugs in the 2.5.x md driver.

#29 lore raw
In reply to Jens Axboe
Quoted 8 lines · Jens Axboe
Quoted 3 lines · Andre Hedrick

So lets dirty list the one drive by Paul G. and be done. Can we do that?

Who cares, really? There's not much point in doing it, we're talking 248 vs 256 sectors in reality. I think it's a _bad_ idea, lets just keep it at 255 and avoid silly drive bugs there.

255 trashes your performance, 128 will perform far better with most setups. This is especially true with raid setups. I'd much rather we got the IDE layer using 256 block writes even if we have to limit it to more modern drives by some handwaving (8Gb+ say)

Alan

#30 lore raw
Quoted 6 lines · Alan Cox
Quoted 5 lines · Jens Axboe
Quoted 3 lines · Andre Hedrick

So lets dirty list the one drive by Paul G. and be done. Can we do that?

Quoted 6 lines
Quoted 3 lines

Who cares, really? There's not much point in doing it, we're talking 248 vs 256 sectors in reality. I think it's a _bad_ idea, lets just keep it at 255 and avoid silly drive bugs there.

255 trashes your performance, 128 will perform far better with most setups. This is especially true with raid setups. I'd much rather we

Then go with 128. I'd like to stress again that _if_ you get worse performance it's not due to the request being a bit smaller, but indeed because 248 can cause badly aligned requests.

Quoted 2 lines

got the IDE layer using 256 block writes even if we have to limit it to more modern drives by some handwaving (8Gb+ say)

Does Windows use 256 sector requests or not? If not, then I'd sure don't want to do it in Linux, the handwaving doesn't mean anything then.

Signature · 1 line
Jens Axboe
#31 lore raw
Quoted 9 lines · Jens Axboe

Then go with 128. I'd like to stress again that _if_ you get worse performance it's not due to the request being a bit smaller, but indeed because 248 can cause badly aligned requests.

Quoted 2 lines

got the IDE layer using 256 block writes even if we have to limit it to more modern drives by some handwaving (8Gb+ say)

Does Windows use 256 sector requests or not? If not, then I'd sure don't want to do it in Linux, the handwaving doesn't mean anything then.

I am told it does, Andre can you confirm this either way. If not then its time to ask vendors to confirm and any vendor who says "our drives are fine" we put on the ok list.

#32 lore raw
Quoted 8 lines · Alan Cox
Quoted 7 lines · Jens Axboe

Then go with 128. I'd like to stress again that _if_ you get worse performance it's not due to the request being a bit smaller, but indeed because 248 can cause badly aligned requests.

Quoted 2 lines

got the IDE layer using 256 block writes even if we have to limit it to more modern drives by some handwaving (8Gb+ say)

Quoted 6 lines
Quoted 2 lines

Does Windows use 256 sector requests or not? If not, then I'd sure don't want to do it in Linux, the handwaving doesn't mean anything then.

I am told it does, Andre can you confirm this either way. If not then its time to ask vendors to confirm and any vendor who says "our drives are fine" we put on the ok list.

Well I can hook an analyzer to such a bastard and verify it for sure, that's one way :)

If Windows does, then we have nothing to worry about.

Signature · 1 line
Jens Axboe