All scsi_debug devices in the scsi_debug driver share the same RAM space
Hello Doug
I had emailed you earlier about this issue forgetting to copy others.
All test devices in the scsi_debug driver share the same ram space so we cannot really have individual devices for testing stuff like md- raid.
I bumped into this a few times already and I think it would be useful to make each device an individual RAM entry so we can create multiple unique devices.
Of course this means also now having to maybe start using attributes for each device do we can selectively choose which devices get the fault injections.
I know its adding complexity here but wanted to get input about the possibility of changing this.
For a particular fault injection case this morning I had to use 5 regular drives and 1 scsi-debug drive to inject faults to reproduce an md-raid issue.
I also wanted a different start sector and range and sent an earlier patch for that.
So is this something worth considering ?
If so, i will start working on it.
Regards
Laurence
Quoted 24 lines · Laurence Oberman
Hello Doug
I had emailed you earlier about this issue forgetting to copy others.
All test devices in the
scsi_debugdriver share the same ram space so we cannot really have individual devices for testing stuff like md- raid.I bumped into this a few times already and I think it would be useful to make each device an individual RAM entry so we can create multiple unique devices.
Of course this means also now having to maybe start using attributes for each device do we can selectively choose which devices get the fault injections.
I know its adding complexity here but wanted to get input about the possibility of changing this.
For a particular fault injection case this morning I had to use 5 regular drives and 1 scsi-debug drive to inject faults to reproduce an
md-raid issue.
Quoted 12 lines
I also wanted a different start sector and range and sent an earlier patch for that.
So is this something worth considering ?
If so, i will start working on it.Regards
Laurence
I chatted with Doug about this.
Seems that many of the use cases for scsi_debug involved creating high count devices for testing etc. so having each with its own ram space could land up chewing a bunch of memory.
I am going to drop this idea for now, but the patch I sent for the choice of sector for MEDIUM errors and count is very useful so I hope that one gets accepted.
That patch changes nothing if the two new parameters are not set so should be low risk for acceptance.
Thanks
Laurence
Hi,
I like the idea to have an option to separate the memory area for different LUNs, while keeping the current behavior as default.
Lukas
Lukas,
Quoted 2 lines
I like the idea to have an option to separate the memory area for different LUNs, while keeping the current behavior as default.
As the name implies, scsi_debug is mostly a tool for debugging the SCSI stack.
If you care about storing data, why not simply use target in loopback mode?
Signature · 1 line
Martin K. Petersen Oracle Linux Engineering
Quoted 5 lines · Martin K. Petersen
Lukas,
Quoted 2 lines
I like the idea to have an option to separate the memory area for different LUNs, while keeping the current behavior as default.
Quoted 7 lines
As the name implies,
scsi_debugis mostly a tool for debugging the SCSI
stack.If you care about storing data, why not simply use target in loopback mode?
Hi Martin
I think what Lukas was really looking for is what I started out wanting.
Individual devices that could be put into configurations such as md- raid for testing and could be used with fault injection.
In the end I had to use 5 (LIO or physical) devices and 1 scsi_debug device to reproduce an issue for md-raid.
Target loopback was an option too.
I have fault injection in qla2xxx tcm already but not in the target core.
I guess it time i look into that now so will proceed with that.
Regards
Laurence