[opensuse] the new openSUSE kernel and the IDE
hi all ! Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"... Why is this? Does it means that the kernel's SCSI module is now used for IDE Hard Disks ? If so, then it's used for all media types: SCSI/IDE Hard Disks, CD Burners, USB Flash Disks, etc... am I correct ? Is there some link that explain this change in behavior ? (at user level, not programmer level) -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 14 Apr 2007, Alexey Eremenko wrote:
hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
Why is this?
Does it means that the kernel's SCSI module is now used for IDE Hard Disks ?
If so, then it's used for all media types: SCSI/IDE Hard Disks, CD Burners, USB Flash Disks, etc... am I correct ?
Is there some link that explain this change in behavior ? (at user level, not programmer level)
-- -Alexey Eremenko "Technologov"
As its a Alpha release, have you checked the "known issues" regarding the release? It may be a bug or a feature, you'll need to check -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
As its a Alpha release, have you checked the "known issues" regarding the release? It may be a bug or a feature, you'll need to check
No, friend, I have checked with the latest ArchLinux distro - other distros have the same problem.... I think It's due to the new kernel. -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 14 April 2007 16:54, ianseeks wrote:
On Saturday 14 Apr 2007, Alexey Eremenko wrote:
hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
Why is this?
Does it means that the kernel's SCSI module is now used for IDE Hard Disks ?
If so, then it's used for all media types: SCSI/IDE Hard Disks, CD Burners, USB Flash Disks, etc... am I correct ?
Is there some link that explain this change in behavior ? (at user level, not programmer level)
-- -Alexey Eremenko "Technologov"
As its a Alpha release, have you checked the "known issues" regarding the release? It may be a bug or a feature, you'll need to check
Look in the opensuse-announce list for the announcement of Alpha3, or http://en.opensuse.org/Factory/News section Changes between openSUSE 10.3 Alpha 1 and Alpha 2 * libata is now also used for IDE controllers Which is using /dev/sdx for all drives. -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
In the new kernel the use the libATA subsytem. All SATA and PATA devices are now called "sdX" (no more "hdX for PATA). Optical devices are called "srX" _=terry(Denver)=- On Sat, 2007-04-14 at 22:51 +0100, Alexey Eremenko wrote:
hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
Why is this?
Does it means that the kernel's SCSI module is now used for IDE Hard Disks ?
If so, then it's used for all media types: SCSI/IDE Hard Disks, CD Burners, USB Flash Disks, etc... am I correct ?
Is there some link that explain this change in behavior ? (at user level, not programmer level)
-- -Alexey Eremenko "Technologov"
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/14/07, Teruel de Campo MD
In the new kernel the use the libATA subsytem. All SATA and PATA devices are now called "sdX" (no more "hdX for PATA). Optical devices are called "srX"
Since it uses "sdX", is the libATA subsytem based SCSI sytem ? -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ? -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-04-14 16:07, Alexey Eremenko wrote:
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
If you have that many in your system, I think you should consider replacing some of them with much larger drives ;-) -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 08:56 AM 4/15/2007, Darryl Gregorash wrote:
On 2007-04-14 16:07, Alexey Eremenko wrote:
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
If you have that many in your system, I think you should consider replacing some of them with much larger drives ;-)
THIS IS NOT A FLAME, but.... personally this change seriously makes me worry I have scripts and software that create drives with links to those in other systems as part of the security and backup routines I use, some are to scsi drives, some are ide and some sata, the drive type in most cases relates to the function performed on the site or spanning sites Before I can consider going to 10.3 :- I shall have to scan, amend, rewrite, binfile at least 20 scripts for cross connection, another 38 for backup and seven security plus workout how I get around the drive type and now limited drive identity\numbers problem and that's just the linux side, how my mini's deal with it I am yet to imagine, thankfully I don't have any mainframes any more. I also suspect it means some ten to twelve thousand dollars additional hardware needed per site, say a quarter of a million dollars plus extra at the four centres and spares of course. I wouldn't of minded the change if the old way worked as well (dual modes) until things were changed with a boot script "software switch" I'd also would have liked some warning, (and I suspect others in the same boat would also have,) well in advance this type of change was going to happen, surely someone was aware this major change was coming and could have put out a notice to users/programmers. It's not as if this is a minor change hda has been around since the ST408/512 drive chains were created It means I have at least 200 hours of work ahead in mapping out the changes needed, let alone arranging things like programming, testing, reviewing, issuing, checking...etc., say another hundred or so thousand dollars Well there goes my holiday this year again, and just as I thought things were finally starting to slow down. I am suppose to be semi-retired It also means 10.2 will have to last at least two years when we implement it at Christmas 07, replacing 8 Maybe we should think sled, but we don't have the money for both, we are ?suppose to be self sufficent and non-profit! scsijon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
scsijon wrote:
[...] I have scripts and software that create drives with links to those in other systems as part of the security and backup routines I use, some are to scsi drives, some are ide and some sata, the drive type in most cases relates to the function performed on the site or spanning sites
Before I can consider going to 10.3 :- I shall have to scan, amend, rewrite, binfile at least 20 scripts for cross connection, another 38 for backup and seven security plus workout how I get around the drive type and now limited drive identity\numbers problem and that's just the linux side, how my mini's deal with it I am yet to imagine, thankfully I don't have any mainframes any more. I also suspect it means some ten to twelve thousand dollars additional hardware needed per site, say a quarter of a million dollars plus extra at the four centres and spares of course. [...]
Frankly, I would consider your backup strategy as broken if it relies on a particular hardware being available as hd? instead of sd?. Of course, it's difficult to say without knowing the details, but it sounds rather strange. Maybe your backup etc. strategy is designed in a suboptimal way. What would happen if your backup server broke down and you had to switch to another one with different hardware? Would you have to change all your backup scripts, etc.? That should not happen. If we have to change our backup servers in the company, it's a matter of seconds not "at least 200 hours of work ahead"... CU, Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Also you could use symlinks... -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 15 April 2007 13:07, Alexey Eremenko wrote:
Also you could use symlinks...
-- -Alexey Eremenko "Technologov"
Just as note, 10.3 alpha mounts disk by name, or by disk label, or few other methods. There is no /dev/sdX in fstab, but some long name ending with part1, 2, 3 etc. In this way is solved problem with new storage media that have no fixed connection point in computer, but device is assigned as it is recognized, or connected. -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/15/07, scsijon
At 08:56 AM 4/15/2007, Darryl Gregorash wrote:
On 2007-04-14 16:07, Alexey Eremenko wrote:
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
If you have that many in your system, I think you should consider replacing some of them with much larger drives ;-)
THIS IS NOT A FLAME, but....
personally this change seriously makes me worry
I have scripts and software that create drives with links to those in other systems as part of the security and backup routines I use, some are to scsi drives, some are ide and some sata, the drive type in most cases relates to the function performed on the site or spanning sites
Before I can consider going to 10.3 :- I shall have to scan, amend, rewrite, binfile at least 20 scripts for cross connection, another 38 for backup and seven security plus workout how I get around the drive type and now limited drive identity\numbers problem and that's just the linux side, how my mini's deal with it I am yet to imagine, thankfully I don't have any mainframes any more. I also suspect it means some ten to twelve thousand dollars additional hardware needed per site, say a quarter of a million dollars plus extra at the four centres and spares of course.
I wouldn't of minded the change if the old way worked as well (dual modes) until things were changed with a boot script "software switch"
I'd also would have liked some warning, (and I suspect others in the same boat would also have,) well in advance this type of change was going to happen, surely someone was aware this major change was coming and could have put out a notice to users/programmers. It's not as if this is a minor change hda has been around since the ST408/512 drive chains were created
It means I have at least 200 hours of work ahead in mapping out the changes needed, let alone arranging things like programming, testing, reviewing, issuing, checking...etc., say another hundred or so thousand dollars
Well there goes my holiday this year again, and just as I thought things were finally starting to slow down. I am suppose to be semi-retired
It also means 10.2 will have to last at least two years when we implement it at Christmas 07, replacing 8
Maybe we should think sled, but we don't have the money for both, we are ?suppose to be self sufficent and non-profit!
scsijon
I was just thinking about how a new OS release is going to cost you a huge amount of time and money. Basically the reason is you are using a Linux Enthusiasts distro as a datacenter solution which you are apparently investing millions of dollars of hardware/software/customization around. You should really evaluate SLES 10.0. It is expensive compared to OpenSUSE, but it is extremely cheap compared to what you describe. If you implemented it now you would have another 4 years or so of supported service. (iirc) Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 06:36 AM 4/18/2007, Greg Freemyer wrote:
On 4/15/07, scsijon
wrote: At 08:56 AM 4/15/2007, Darryl Gregorash wrote:
On 2007-04-14 16:07, Alexey Eremenko wrote:
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
If you have that many in your system, I think you should consider replacing some of them with much larger drives ;-)
THIS IS NOT A FLAME, but....
personally this change seriously makes me worry
I have scripts and software that create drives with links to those in other systems as part of the security and backup routines I use, some are to scsi drives, some are ide and some sata, the drive type in most cases relates to the function performed on the site or spanning sites
Before I can consider going to 10.3 :- I shall have to scan, amend, rewrite, binfile at least 20 scripts for cross connection, another 38 for backup and seven security plus workout how I get around the drive type and now limited drive identity\numbers problem and that's just the linux side, how my mini's deal with it I am yet to imagine, thankfully I don't have any mainframes any more. I also suspect it means some ten to twelve thousand dollars additional hardware needed per site, say a quarter of a million dollars plus extra at the four centres and spares of course.
I wouldn't of minded the change if the old way worked as well (dual modes) until things were changed with a boot script "software switch"
I'd also would have liked some warning, (and I suspect others in the same boat would also have,) well in advance this type of change was going to happen, surely someone was aware this major change was coming and could have put out a notice to users/programmers. It's not as if this is a minor change hda has been around since the ST408/512 drive chains were created
It means I have at least 200 hours of work ahead in mapping out the changes needed, let alone arranging things like programming, testing, reviewing, issuing, checking...etc., say another hundred or so thousand dollars
Well there goes my holiday this year again, and just as I thought things were finally starting to slow down. I am suppose to be semi-retired
It also means 10.2 will have to last at least two years when we implement it at Christmas 07, replacing 8
Maybe we should think sled, but we don't have the money for both, we are ?suppose to be self sufficent and non-profit!
scsijon
I was just thinking about how a new OS release is going to cost you a huge amount of time and money. Basically the reason is you are using a Linux Enthusiasts distro as a datacenter solution which you are apparently investing millions of dollars of hardware/software/customization around.
You should really evaluate SLES 10.0. It is expensive compared to OpenSUSE, but it is extremely cheap compared to what you describe. If you implemented it now you would have another 4 years or so of supported service. (iirc)
Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century
to answer a number of comments together. 1/ unfortunately I have "absolutely" no control or input in the software $$$$, I fought and lost this battle when SLES9 came out and we were using 7.2. I have been given some control on the hardware $$ though, so the users are at least not using P2's any more and have decent screens (35w 19"LCD vs 340w 17" tube power use, does talk money saving in the budget meeting). 2/ the scripts are unfortunately messy and due to a level of management paranoia, have to be individually coded else there would only be three. They contain test and checks against failure of hardware and cross site links and include such bits as disabling / enabling backup links in the routers if paths fail. e.g. backups go to two remote devices (one interstate) as well as the local tape silo. 3/ With downsizing that has happened due to the net, i've been waiting for site shutdowns to ocurr, but they seem to prefer to use the, "large number of sites with small number of staff in each model", at least. scsijon
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 14 April 2007 15:07, Alexey Eremenko wrote:
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
The universe will implode. Please don't do that.
-- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/14/07, Alexey Eremenko
What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
I tried to put a bunch of 2-channel IDE controllers in a SUSE box a couple years ago. I found that you run out of supported channels before you run out of drive letters. When I tried to actually do some performance testing (dd bs=4k if=/dev/zero of=/dev/hdX to lots of drives) I found the performance dropped off rapidly with lots of simultaneous disk activity. I chalked it up to running out of PCI-bus bandwidth, but I don't really know. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/15/07, Greg Freemyer
On 4/14/07, Alexey Eremenko
wrote: What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
I tried to put a bunch of 2-channel IDE controllers in a SUSE box a couple years ago.
OK, but some servers with massive SCSI arrays may have well over 26 disks... -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/14/07, Alexey Eremenko
On 4/15/07, Greg Freemyer
wrote: On 4/14/07, Alexey Eremenko
wrote: What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
I tried to put a bunch of 2-channel IDE controllers in a SUSE box a couple years ago.
OK, but some servers with massive SCSI arrays may have well over 26 disks...
Unlikely, those massive arrays virtualize the disk subsystem and make it look like a much smaller set of drives to the OS. ie. a 10-disk hardware raid-5 looks like one disk to the OS. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Alexey Eremenko wrote:
On 4/15/07, Greg Freemyer
wrote: On 4/14/07, Alexey Eremenko
wrote: What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
I tried to put a bunch of 2-channel IDE controllers in a SUSE box a couple years ago.
OK, but some servers with massive SCSI arrays may have well over 26 disks...
From working at a large corporation, and having seen Linux devices (not SuSE in particular) having lots of SAN disks, the format goes to sdaa, sdab...
Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2007-04-15 at 01:07 +0100, Alexey Eremenko wrote:
On 4/15/07, Greg Freemyer
wrote: On 4/14/07, Alexey Eremenko
wrote: What will happen after "sdX" reaches from sda to sdz ? i.e. if you have over 26 hard disks in your system ?
I tried to put a bunch of 2-channel IDE controllers in a SUSE box a couple years ago.
OK, but some servers with massive SCSI arrays may have well over 26 disks...
USB disks are also called sdX. As are firewire. So, add the IDE, SCSI, USB and firewire disks and 26 can (and will) happen shortly. Of course, prior to this change SCSI, USB and firewire were already sdX. So it is only the few IDE disks that have been added to the total. I like the change. As long as the BUS id ("scsi", "usbdisk", etc) remains so I can tell which is which in udev.
-- -Alexey Eremenko "Technologov" -- Roger Oberholtzer
OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/14/07, Alexey Eremenko
hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
Why is this?
I believe in 2.6.21-rcX the libata / pata support is still marked experimental overall, but it is rapidly maturing and 2.6.22 may lose that designation. Someone else recently said that the next full OpenSUSE release would not be until the fall. If so, the OpenSUSE team may be expecting to use libata for PATA at that point and want to start getting it exposed to users. If you would like to still use the traditional drivers/ide subsection it should be easy to recompile a reconfigured kernel from the sources. i.e the source code should still be there.
Does it means that the kernel's SCSI module is now used for IDE Hard Disks ?
libata uses the scsi infrastructure, but less and less.
If so, then it's used for all media types: SCSI/IDE Hard Disks, CD Burners, USB Flash Disks, etc... am I correct ?
I think so, but it is a compile time option for PATA drives.
Is there some link that explain this change in behavior ? (at user level, not programmer level)
Don't know of one. The biggest 2 changes I know of beyond naming convention are: libata supports fewer partitions per drive (16?) libata does not yet support HPA overriding. This is important because if a user is using that feature in the old drivers/ide setup, then libata will not be useable for them.
-- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-04-14 at 20:12 -0400, Greg Freemyer wrote:
The biggest 2 changes I know of beyond naming convention are:
libata supports fewer partitions per drive (16?)
15, in fact. And I have 20, so I can't use that suse version.
- From the official announce a month ago:
Date: Thu, 15 Mar 2007 17:09:04 +0100
From: Andreas Jaeger
To:
On 4/14/07, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2007-04-14 at 20:12 -0400, Greg Freemyer wrote:
The biggest 2 changes I know of beyond naming convention are:
libata supports fewer partitions per drive (16?)
15, in fact. And I have 20, so I can't use that suse version.
- From the official announce a month ago:
Date: Thu, 15 Mar 2007 17:09:04 +0100 From: Andreas Jaeger To:
Subject: [opensuse-announce] openSUSE 10.3 Alpha2 Release I'm glad to announce the second public alpha release of openSUSE 10.3.
...
We're using the libata stack now also for IDE controllers. Please do test that an update works and all files are changed automatically (libata uses /dev/sda for the first harddisk instead of /dev/hda). Disks with more than 15 partitions are not handled right now, we're still evaluating whether there is a good solution. to use the old scheme, boot with "hwprobe=-modules.pata". See below for Bug 250241 as well.
- -- Cheers, Carlos E. R.
Carlos,
Within the last week I saw a posting on the libata list from Alan Cox
that as soon as the HPA issue was addressed he considered the
libata/pata subsystem feature equivalent with the old drivers/ide
subsystem. He made no mention of the 15 partition limit, so if you
think that it is a significant issue, you should say something.
Alan is with RedHat, but he was the 2.4 drivers/ide maintainer (I
think), and he has definitely been the person pushing the libata/pata
move.
You can post directly to "Linux-ide"
On 2007/04/15 02:44 (GMT+0200) Carlos E. R. apparently typed:
The Saturday 2007-04-14 at 20:12 -0400, Greg Freemyer wrote:
The biggest 2 changes I know of beyond naming convention are:
libata supports fewer partitions per drive (16?)
15, in fact. And I have 20, so I can't use that suse version.
Why not....
- From the official announce a month ago: to use the old scheme, boot with "hwprobe=-modules.pata".
The modules.pata scheme works for my 25 partition disks. -- "Therefore, if anyone is in Christ, he is a new creation; the old has gone, the new has come!" 2 Corinthians 5:17 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-04-14 at 23:13 -0400, Felix Miata wrote:
libata supports fewer partitions per drive (16?)
15, in fact. And I have 20, so I can't use that suse version.
Why not....
Because five partitions will not be seen. At worst, something like Yast could get confused and hose my disk. Andreas Jaeger told me in the Factory list to wait till they have a solution. Therefore, I'm waiting.
- From the official announce a month ago: to use the old scheme, boot with "hwprobe=-modules.pata".
The modules.pata scheme works for my 25 partition disks.
Why didn't you say so when I I was told not to even try? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGIgLmtTMYHG2NR9URAqnCAJ9buNTEMD1wruzopkvfe2c+hbTb3ACeMMRX 8RNgHw1qvijESbaK2MWsjKU= =vW/I -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Should we, as a community, take some steps to ensure best experience for our Susers ? (SUSE users) :) One thing that comes to mind, is to symlink (or even hardlink?) sda block devices to hda files, so that suser's transition will be transparent. This will NOT solve the 15-partitions problem, but this *will* save all the fstabs, backup scripts and other system software from braking with a new openSUSE release. This should be made as a backward-compatibility measure. What do you think of it? -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Should we, as a community, take some steps to ensure best experience for our Susers ? (SUSE users) :) One thing that comes to mind, is to symlink (or even hardlink?) sda block devices to hda files, so that suser's transition will be transparent.
I really think this is a non-issue; there is a long existing solution to this problem: LVM. Drives are scanned and assigned to volume groups dynamically. Use LVM.
This will NOT solve the 15-partitions problem, but this *will* save
I strongly suspect that 15 partitions per drives is *extremely* rare. Use LVM and you can carve up your disks as many ways as you want.
all the fstabs, backup scripts and other system software from braking with a new openSUSE release. This should be made as a backward-compatibility measure.
-- -- Adam Tauno Williams Network & Systems Administrator Consultant - http://www.whitemiceconsulting.com Developer - http://www.opengroupware.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/15/07, Adam Tauno Williams
Should we, as a community, take some steps to ensure best experience for our Susers ? (SUSE users) :) One thing that comes to mind, is to symlink (or even hardlink?) sda block devices to hda files, so that suser's transition will be transparent.
I really think this is a non-issue; there is a long existing solution to this problem: LVM. Drives are scanned and assigned to volume groups dynamically.
Use LVM.
This will NOT solve the 15-partitions problem, but this *will* save
I strongly suspect that 15 partitions per drives is *extremely* rare.
Use LVM and you can carve up your disks as many ways as you want.
all the fstabs, backup scripts and other system software from braking with a new openSUSE release. This should be made as a backward-compatibility measure.
LVM is a non-solution. It doesn't supports Windows interoperability. Same goes for SoftRAID. I need to stay Windows compatible. -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 15 April 2007, Alexey Eremenko wrote:
LVM is a non-solution. I
Well said. The Church of LVM Saints seems to push its way to the front every time there is any issue involving disk. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Alexey Eremenko wrote:
On 4/15/07, Adam Tauno Williams
wrote: Should we, as a community, take some steps to ensure best experience for our Susers ? (SUSE users) :) One thing that comes to mind, is to symlink (or even hardlink?) sda block devices to hda files, so that suser's transition will be transparent.
I really think this is a non-issue; there is a long existing solution to this problem: LVM. Drives are scanned and assigned to volume groups dynamically.
Use LVM.
This will NOT solve the 15-partitions problem, but this *will* save
I strongly suspect that 15 partitions per drives is *extremely* rare.
Use LVM and you can carve up your disks as many ways as you want.
all the fstabs, backup scripts and other system software from braking with a new openSUSE release. This should be made as a backward-compatibility measure.
LVM is a non-solution. It doesn't supports Windows interoperability. Same goes for SoftRAID. I need to stay Windows compatible.
In what way is your linux partition setup "windows compatible"? I what way does LVM spoil your "Windows Compatibility"? regards Eberhard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-04-15 at 23:14 +0100, Alexey Eremenko wrote:
Should we, as a community, take some steps to ensure best experience for our Susers ? (SUSE users) :)
One thing that comes to mind, is to symlink (or even hardlink?) sda block devices to hda files, so that suser's transition will be transparent.
I'm sure that's being addressed. The fstab and grub will not break, at least. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGIryHtTMYHG2NR9URAvzBAJsFiT8uMT5el1D/q35kCI2s1HhjLgCbBC9S 1VSCpGN2sw+lPh+/JRVFt7o= =++z/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 15 April 2007 19:00, Carlos E. R. wrote:
I'm sure that's being addressed. The fstab and grub will not break, at least.
The default fstab doesn't look like it was before in 10.3 Alpha. There is no /dev/sdX, but long disk name ending with part1,2,3 etc. -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-04-15 at 20:59 -0500, Rajko M. wrote:
On Sunday 15 April 2007 19:00, Carlos E. R. wrote:
I'm sure that's being addressed. The fstab and grub will not break, at least.
The default fstab doesn't look like it was before in 10.3 Alpha. There is no /dev/sdX, but long disk name ending with part1,2,3 etc.
Like this one? /dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15 I mount some of my partitions that way (in /etc/cryptotab), and some by label (in /etc/fstab): LABEL=320_boot1 /boot ext2 noatime,acl,user_xattr 0 0 both systems are independent of how or where the disk is mounted. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGJWRDtTMYHG2NR9URAmU5AJ9K0K++EIiQPE5iZxjTgka4sC5O2ACgj/VZ gnuZCGo3qS4odONKdDPtxBM= =8qG6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 10:20 AM 4/18/2007, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-04-15 at 20:59 -0500, Rajko M. wrote:
On Sunday 15 April 2007 19:00, Carlos E. R. wrote:
I'm sure that's being addressed. The fstab and grub will not break, at least.
The default fstab doesn't look like it was before in 10.3 Alpha. There is no /dev/sdX, but long disk name ending with part1,2,3 etc.
Like this one?
/dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15
I mount some of my partitions that way (in /etc/cryptotab), and some by label (in /etc/fstab):
LABEL=320_boot1 /boot ext2 noatime,acl,user_xattr 0 0
both systems are independent of how or where the disk is mounted.
- -- Cheers, Carlos E. R.
Carlos (and others (?aj)), can you check / could you check / have you checked? if you had the drive listed above die and had to use a new drive and reload from a backup (simple to do to here) ?would the id part "5QF2M56F" have to be changed (I suspect this is the drive's internal I.D.) for it to work? It looks like a good additional level for security but does worry me for device failure rework. thanks It would also allow all of drives to exist on a site to be available to the workstation as part of the start process (i.e. workstation with swap partition only and all others on a server matrix of drives) coded from grub scsijon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 18 April 2007 20:03, scsijon wrote:
At 10:20 AM 4/18/2007, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-04-15 at 20:59 -0500, Rajko M. wrote:
On Sunday 15 April 2007 19:00, Carlos E. R. wrote:
I'm sure that's being addressed. The fstab and grub will not break, at least.
The default fstab doesn't look like it was before in 10.3 Alpha. There is no /dev/sdX, but long disk name ending with part1,2,3 etc.
Like this one?
/dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15
I mount some of my partitions that way (in /etc/cryptotab), and some by label (in /etc/fstab):
LABEL=320_boot1 /boot ext2 noatime,acl,user_xattr 0 0
both systems are independent of how or where the disk is mounted.
- -- Cheers, Carlos E. R.
Carlos (and others (?aj)), can you check / could you check / have you checked?
if you had the drive listed above die and had to use a new drive and reload from a backup (simple to do to here)
?would the id part "5QF2M56F" have to be changed (I suspect this is the drive's internal I.D.) for it to work?
By now you should have used YaST to include drive in system and you have exact
naming already in a fstab, but to avoid problems with backup scripts, I would
use second form LABEL=
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-04-19 at 11:03 +1000, scsijon wrote:
/dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15
Carlos (and others (?aj)), can you check / could you check / have you checked?
if you had the drive listed above die
and had to use a new drive
and reload from a backup (simple to do to here)
?would the id part "5QF2M56F" have to be changed (I suspect this is the drive's internal I.D.) for it to work?
Yes, that's correct. The "ST3320620A" above is the disk model (seagate st etc), the second word I guess it is a serial number. If that worries you, then use labels instead - but in that case, you can mount two partitions with the same label in order to copy data from one to the other.
It looks like a good additional level for security but does worry me for device failure rework.
Depends on what your procedure is. The label is dependent on the formated filesystem, it is saved somewhere there. If a partition is badly hosed, the label is lost: I know because it happened to me. The disk ID is more resistant, and it is usable in the cryptotab file (label mounting doesn't work there). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGJ0ixtTMYHG2NR9URAhfaAJ9RR/VVDf3RdfbpPVZ75LGb40sqmwCeKKOl gWbEOUlZ0J1BkKbViYmT0Dc= =EcIy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 08:47 PM 4/19/2007, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2007-04-19 at 11:03 +1000, scsijon wrote:
/dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15
Carlos (and others (?aj)), can you check / could you check / have you checked?
if you had the drive listed above die
and had to use a new drive
and reload from a backup (simple to do to here)
?would the id part "5QF2M56F" have to be changed (I suspect this is the drive's internal I.D.) for it to work?
Yes, that's correct. The "ST3320620A" above is the disk model (seagate st etc), the second word I guess it is a serial number.
If that worries you, then use labels instead - but in that case, you can mount two partitions with the same label in order to copy data from one to the other.
It looks like a good additional level for security but does worry me for device failure rework.
Depends on what your procedure is.
The label is dependent on the formated filesystem, it is saved somewhere there. If a partition is badly hosed, the label is lost: I know because it happened to me.
The disk ID is more resistant, and it is usable in the cryptotab file (label mounting doesn't work there).
- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76
thanks scsijon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Speaking of the /dev/hda issue - it affects even SUSE's own modules: (IDE Acceleration Yast Module) link: https://bugzilla.novell.com/show_bug.cgi?id=264681 I definitely think that we need to symlink or hardlink the new devices to the old names in 10.3. -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 17 April 2007 19:20, Carlos E. R. wrote:
The Sunday 2007-04-15 at 20:59 -0500, Rajko M. wrote:
On Sunday 15 April 2007 19:00, Carlos E. R. wrote:
I'm sure that's being addressed. The fstab and grub will not break, at least.
The default fstab doesn't look like it was before in 10.3 Alpha. There is no /dev/sdX, but long disk name ending with part1,2,3 etc.
Like this one?
/dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15
I mount some of my partitions that way (in /etc/cryptotab), and some by label (in /etc/fstab):
LABEL=320_boot1 /boot ext2 noatime,acl,user_xattr 0 0
both systems are independent of how or where the disk is mounted.
Yes. The first one is default, but I changed it to something that I know how to handle :-) -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Alexey Eremenko escribió:
hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
it you stop posting 500 times per second and take some time read the archives and the release notes, you will find that this is the expected behaviuor due to the use of libata by default.
"Alexey Eremenko"
hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
Why is this?
Did you read my announcement at all? Call for Testing ================ * libata for IDE devices We're using the libata stack now also for IDE controllers. Please do test that an update works and all files are changed automatically (libata uses /dev/sda for the first harddisk instead of /dev/hda). Disks with more than 15 partitions are not handled right now, we're still evaluating whether there is a good solution. to use the old scheme, boot with "hwprobe=-modules.pata". Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Mon April 16 2007, Andreas Jaeger scratched these words onto a coconut shell, hoping for an answer:
"Alexey Eremenko"
writes: hi all !
Just installed openSUSE 10.3 Alpha3 with the new kernel 2.6.21-rc... The problem is that all my IDE hard disks are displayed as "sda"...
Why is this?
Did you read my announcement at all?
Call for Testing ================
* libata for IDE devices
We're using the libata stack now also for IDE controllers. Please do test that an update works and all files are changed automatically (libata uses /dev/sda for the first harddisk instead of /dev/hda). Disks with more than 15 partitions are not handled right now, we're still evaluating whether there is a good solution. to use the old scheme, boot with "hwprobe=-modules.pata".
Andreas Andreas, You were expecting people to read the documentation ??? Silly, no one EVER reads that stuff... ;-)
How many timesdo we have the same stupid *discussion*about the need for hard copies of documentation vs, "just get rid of it all, I never read any of that stuff, its a waste of money to write and print it. " The two sides of this aurgume... uh, no, rather say disCUSSion , which by now borders on religious zealotry. ( Emphasis on "cussing" intended, as it often falls just short of what the list gods will tolerate for language. ) I suspect a lot of the folks who took up your offer of really early software that needs testing ( alpha, let alone betas ), didn't even notice the way you described the items. In some ways you probably get a better cross section of *real life* users testing it. Of course this sort of users wasn't what you were looking for .Those that just want the very latest, hottest, most far out from the center as they can get.. and there will be many of them who send you strange reports of broken this or that pieces. I thought your announcement represented exactly what you were looking for in testers. But, you forgot a universal constant of software. "Nobody reads the documentation" Except perhaps one other person,in the world, and me. No matter what documentation you use, nor what you say when you let it leave your hand, will in any way prevent people in the future, when your products go gold again, complaining bout strange things you weren't even concerned w/. From the "this software burned my house down" to "what is this software supposed to *do* ? " All variants of user remarks. -- j I've lived in the real world enough, we're all here because we ain't all there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
It is not correct statement, that I don't read documentation. *Sometimes* I do, but this time I really overlooked it. will try harder next time :) -- -Alexey Eremenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jfweber@gilweber.com writes:
You were expecting people to read the documentation ???
No, not really ;-).
Silly, no one EVER reads that stuff... ;-)
I know...
[...] Of course this sort of users wasn't what you were looking for .Those that just want the very latest, hottest, most far out from the center as they can get.. and there will be many of them who send you strange reports of broken this or that pieces.
I thought your announcement represented exactly what you were looking for in testers. But, you forgot a universal constant of software. "Nobody reads the documentation" Except perhaps one other person,in the world, and me.
No matter what documentation you use, nor what you say when you let it leave your hand, will in any way prevent people in the future, when your products go gold again, complaining bout strange things you weren't even concerned w/. From the "this software burned my house down" to "what is this software supposed to *do* ? " All variants of user remarks.
If you have a solution for this, I'm willing to hear it. So far I can only try to release working software, calling it loud ALPHA, and pointing to the documentation so that those who complain *might* check next time ;-). Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2007-04-17 01:32, Andreas Jaeger wrote:
jfweber@gilweber.com writes:
<snip>
No matter what documentation you use, nor what you say when you let it leave your hand, will in any way prevent people in the future, when your products go gold again, complaining bout strange things you weren't even concerned w/. From the "this software burned my house down" to "what is this software supposed to *do* ? " All variants of user remarks.
If you have a solution for this, I'm willing to hear it. So far I can only try to release working software, calling it loud ALPHA, and pointing to the documentation so that those who complain *might* check next time ;-). And for your next trick, we expect to see you herding some cats, and teaching some pigs to sing ;-)
-- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-04-16 at 09:19 +0200, Andreas Jaeger wrote:
Did you read my announcement at all?
Call for Testing ================
* libata for IDE devices
We're using the libata stack now also for IDE controllers. Please do test that an update works and all files are changed automatically (libata uses /dev/sda for the first harddisk instead of /dev/hda). Disks with more than 15 partitions are not handled right now, we're still evaluating whether there is a good solution. to use the old scheme, boot with "hwprobe=-modules.pata".
Question. With "hwprobe=-modules.pata", are more than 15 partitions supported? If yes, then, Q #2: When there are more than 15 partitions, will this situation be detected and then automatically activate "hwprobe=-modules.pata", or do we have to add that manually when booting the install dvd? At least till a better, definitive solution is found. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGJWdRtTMYHG2NR9URAjsbAJ9Dxwmg6K9BiOQ/or86RaAsiGa+7QCfRBB9 kR5WD36qSIOhiVVKO2uLeE4= =yEev -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
"Carlos E. R."
The Monday 2007-04-16 at 09:19 +0200, Andreas Jaeger wrote:
Did you read my announcement at all?
Call for Testing ================
* libata for IDE devices
We're using the libata stack now also for IDE controllers. Please do test that an update works and all files are changed automatically (libata uses /dev/sda for the first harddisk instead of /dev/hda). Disks with more than 15 partitions are not handled right now, we're still evaluating whether there is a good solution. to use the old scheme, boot with "hwprobe=-modules.pata".
Question. With "hwprobe=-modules.pata", are more than 15 partitions supported?
If yes, then, Q #2:
Yes.
When there are more than 15 partitions, will this situation be detected and then automatically activate "hwprobe=-modules.pata", or do we have to add that manually when booting the install dvd?
At least till a better, definitive solution is found.
We're working on a better solution for this (which does not involved using the old ata stack - hwprobe=-modules.pata uses the old stack - but until this is in place, this is the manual workaround. So, for now, please add it manually, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wed, 18 Apr 2007, Carlos E. R. wrote:
Question. With "hwprobe=-modules.pata", are more than 15 partitions supported?
If yes, then, Q #2:
Yes.
When there are more than 15 partitions, will this situation be detected and then automatically activate "hwprobe=-modules.pata", or do we have to
Interesting idea. Steffen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (21)
-
Adam Tauno Williams
-
Alexey Eremenko
-
Andreas Jaeger
-
Carlos E. R.
-
Cristian Rodriguez R.
-
Darryl Gregorash
-
Druid
-
Eberhard Roloff
-
Felix Miata
-
Greg Freemyer
-
ianseeks
-
jfweber@gilweber.com
-
John Andersen
-
Michael Letourneau
-
Rajko M.
-
Randall R Schulz
-
Roger Oberholtzer
-
scsijon
-
Steffen Winterfeldt
-
Teruel de Campo MD
-
Thomas Hertweck