Sudhir wrote:

Patrick Shanahan wrote:

...

* JB2 [04-05-08 22:21]:

...

The new hdd is SATA. Will it mess anything up to have an SATA drive and an ide drive on my system like this?

I have five ide drives and three sata drives in this 10.1 system.

I am green with envy :).

It's not hard. Just never throw a drive away until it's dead. Personally, I always use my oldest drive or drives (depending on size and space requirements) for /tmp and swap space. Yes, I know swap SHOULD be a fast device, not some old, device from 2 technology generations ago...but I'll put up with a bit of a speed reduction if it means that I'm NOT beating the hell out of my fastest (i.e. NEWEST) disk drives by putting swap on any of them....because the newer the drive, the more important the data on them. Newest drives filesystem Newest drive(s): /home, /www, and other content created by me or other users of the system /local /opt some things here require more then just an OS re-install to create again. rest of operating system Oldest drive(s): /tmp, swap space How do I do this? Easy. I never buy expensive, huge drives: Why buy a 500 GB drive if I only have 50 GB of data right now?? I can buy a 200 GB drive now for about $45...and by the time I fill that thing up, for another $50 or so, I'll probably get something even bigger than 300 GB. Or, I could spend much more than $95 now to buy the 500GB drive all at once. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Neil wrote:

On Sun, Apr 6, 2008 at 12:54 PM, Sam Clemens wrote:

...

Sudhir wrote:

...

Patrick Shanahan wrote:

...

* JB2 [04-05-08 22:21]:

...

The new hdd is SATA. Will it mess anything up to have an SATA drive and an ide drive on my system like this?

I have five ide drives and three sata drives in this 10.1 system.

I am green with envy :).

It's not hard. Just never throw a drive away until it's dead. Personally, I always use my oldest drive or drives (depending on size and space requirements) for /tmp and swap space.

Yes, I know swap SHOULD be a fast device, not some old, device from 2 technology generations ago...but I'll put up with a bit of a speed reduction if it means that I'm NOT beating the hell out of my fastest (i.e. NEWEST) disk drives by putting swap on any of them....because the newer the drive, the more important the data on them.

Newest drives filesystem

Newest drive(s): /home, /www, and other content created by me or other users of the system

/local

/opt some things here require more then just an OS re-install to create again.

rest of operating system

Oldest drive(s): /tmp, swap space

How do I do this? Easy.

I never buy expensive, huge drives: Why buy a 500 GB drive if I only have 50 GB of data right now?? I can buy a 200 GB drive now for about $45...and by the time I fill that thing up, for another $50 or so, I'll probably get something even bigger than 300 GB.

Or, I could spend much more than $95 now to buy the 500GB drive all at once.

If I am correct and swap space is striped over the different drives it is placed upon then it should matter more how many drives you have with swap spaces on it.

Swap space is striped ONLY if you set it up to be so. If two swap spaces have different priority levels, one swap space will be exhausted before the system starts to use the 2nd one.

True: the access time of old harddisks is worse, but then again: the swap space will probably be used to store the bigger files anyways,

Swapping is not used to "store files"... it's used to page out memory pages so that the CPU can use a larger address space than the amount of physical memory installed (or more specifically: virtual address space = physical mem + swap space) [This ignores annoying things like memory-mapped I/O, etc.]

since Linux is smart in handeling swap space.

smart, yes. magic: no

The access time of a harddisk is always a order of magnitude longer than the acces time of RAM, even with the newest (non solid state) disks, so IF the designers of the daemons that handle the swap space of Linux are as smart as I believe they are then (when swapspace is needed) the largest files will have a larger chance of getting in the swapspace (although there most likely are strong arguments why some files shoudn't be swapped if possible).

But swapping isn't done by file, it's done on a page by page basis. You can have some of a file in memory, some of it swapped out, and some of it not even read yet. And pages to be swapped are evaluated on an individual basis (what's the current page size now...4k? 16k? 54k?) Google for "demand-paged-virtual-memory", and take a look at these: http://en.wikipedia.org/wiki/Paging http://en.wikipedia.org/wiki/Page_replacement_algorithm http://en.wikipedia.org/wiki/Demand_paging Note that Windows has historically NOT used "demand paging"...instead, what they call "aggressive paging" (anticipatory paging also known as prepaging) which in theory works great, but in practice, results in lots of paging activity which is never needed -- it seems to be one of the primary reasons why Windows is so pathatically non-responsive so often -- instead of just paging out what needs to be paged out, and then getting with running your program ... n ooooooooo, it decides to page out more memory, so that it can pre-load code within a branch that never gets executed. [Great plan you got there, Redmondites].

So: the resulting speed of your swap space is probably in lesser extend a result of the actual speed of the harddisk and to greater extend a result of the number of harddisks in swap.

I would have used my new drives for swap space, but you started a train of thougts causing me to reconsider that.Hmm, if I simply use the tower of 1 to 5 G 5400 rpm harddisks to create swap space that might save me from a crash in the future.

If your swap drive dies, you're still going to crash. But if there's nothing else on the disk, at least you're not losing filesystems, too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, Apr 6, 2008 at 10:24 PM, Neil wrote:

...

Swap space is striped ONLY if you set it up to be so. If two swap spaces have different priority levels, one swap space will be exhausted before the system starts to use the 2nd one.

Hmm, what should I do to make the swap space striped? Is there a command in the installer to do so?

Why worry about that? Just put in enough memory and stop obsessing about swap? It will be fine. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Neil wrote:

On Sun, Apr 6, 2008 at 5:54 PM, Sam Clemens wrote:

...

Neil wrote:

...

If I am correct and swap space is striped over the different drives it is placed upon then it should matter more how many drives you have with swap spaces on it.

Swap space is striped ONLY if you set it up to be so. If two swap spaces have different priority levels, one swap space will be exhausted before the system starts to use the 2nd one.

Hmm, what should I do to make the swap space striped? Is there a command in the installer to do so?

To be absolutely positive: Stripe the partitions using LVM or RAID tools Or set two swap partitions with the same priority level (pri=nn where nn is 2-digit value), and then use $ /sbin/swapon -s and see if the usage is split between the two partitions.

...

...

True: the access time of old harddisks is

...

worse, but then again: the swap space will probably be used to store the bigger files anyways,

Swapping is not used to "store files"... it's used to page out memory pages so that the CPU can use a larger address space than the amount of physical memory installed (or more specifically: virtual address space = physical mem + swap space)

[This ignores annoying things like memory-mapped I/O, etc.]

True, storing is not the correct word. I thought Linux was able to see wether a file was big and swap it out completely. If it can't than

Nope. Paging is done by demand. There's no reason to swap out an entire large file if the kernel only needs a couple MB for something else

that is to bad for my theory .If you didn't see that it was a theory then I should be clearer in that in the future. Maybe some fake HTML like tags. I do know swapping is used to create a virtual memory to extend the RAM in times of great need.

On most systems, it's normal. Unusual system requirements aside, if you're never using swap, then you probably overspent on memory. [Conversely, if you're running a moderately large database server, and swap usage is consistently some percentage ( < 50% or so) of the installed RAM, and your performance sucks, then you should immediately install at least as much memory as the typical swap usage.] <snip happens> -- 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 2008-04-06 at 01:01 -0400, Felix Miata wrote:

It easily might. You can generally clone from PATA to PATA and from SATA to SATA in order to replace an old with a new. To clone from PATA to SATA or vice versa is fraught with booby traps.

1-The drivers each uses is usually different.

2-Each PATA can have up to 62 usable partitions. Each SATA can have only 14.

3-The BIOS order of each may not be what you would like, or easy to change to what you might like. This falls through to /dev & grub device order and fstab.

Don't forget that device names change (/dev/hd? <--> /dev/sd?), creating havoc in fstab and/or grub.

You can reduce potential problems by setting labels on your partitions first, then converting fstab and grub to use those labels instead of device names, all before first trying to add a SATA HD to the system.

Right.

Life is simpler if sticking exclusively to one or the other, which may include using hardware adapter(s) to convert one type for use as the other type. -- "Either the constitution controls the judges, or the judges rewrite the constitution." Judge Robert Bork

- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH+JsQtTMYHG2NR9URAu+NAJwPCvmRdnZktpgGxDI93lkULHGUdwCff0t2 9A3CCh3FidzhbJRsqooe8sA= =OcbC -----END PGP SIGNATURE----- -- 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 2008-04-06 at 01:22 -0500, JB2 wrote:

Thanks for all the answers everyone! I feel comfortable about it now. As Felix said though in his post, trying to clone what I have now onto the new drive is a little too iffy for me, so it looks like I'll have to put /home on a DVD and start from scratch (the only reason I hate and dread doing it though is because with dial-up it all takes so darn long...oh well).

You can clone it. It's doable. At least, you can try. You just gotta be very careful. :-) For instance, you may remove the pata disk temporarily, install the sata one, install a small suse partition on it (rest not partitioned yet), reattach the pata, modify fstab, clone the old one to new partitions, adjust grub, try to boot it. If it fails, you have the rescue partition you created first to do rescue operations, and the original pata intact ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH+JwwtTMYHG2NR9URAlZlAJ9CNKAbkSmBXmO81PI1ibpTff451gCglWuQ tt6Lg3WBW2WzeE3E7ktvnP0= =znj8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, 6 Apr 2008 20:08:13 Sam Clemens wrote:

JB2 wrote:

...

On Sat 05 April 08, JB2 wrote:

...

Hiya gang,

One of my hdd's has finally croaked (SMART said it was hardware....made all kinds of wacky noises too).

My main hdd is 80GB and an ide, the new drive is sata 160GB. I got the new drive to replace my main hdd, so I can move the old main one and make it my backup drive.

The new hdd is SATA. Will it mess anything up to have an SATA drive and an ide drive on my system like this?

Thanks for all the answers everyone! I feel comfortable about it now. As Felix said though in his post, trying to clone what I have now onto the new drive is a little too iffy for me, so it looks like I'll have to put /home on a DVD and start from scratch (the only reason I hate and dread doing it though is because with dial-up it all takes so darn long...oh well).

You can easily clone home:

$ su - # change to root password: # type root password $ cd /newhome # or where ever you want to copy /home to. $ (cd /home && tar cvSf - . ) | tar xvSf -

### Interpretation of the 4th line: # In a subshell: ## go to /home and then ## CREATE (c) a tape archive of /tar, #### be VERBOSE (v), optimize SPARSE files (s), #### and send the output to the file "-", which #### is an alias for standard output..

# take the output of that subshell, and pipe it # into the following command (which is being # executed in the original shell, which has ITS # current directory as /newhome): # ## EXTRACT (x) a tar archive, be Verbose (v), ## and optimize the storage of SPARSE files (s), ## reading from the file "-" (standard input, ## which in this case, is the pipe, which is ## the output of the other tar command which ## was executed in the /home directory).

I love how much you can learn on this list. I'm definitely filing this one away for future reference! Never know when I might need this... Thanks, Sam. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== There are people so addicted to exaggeration that they can't tell the truth without lying.

On Sunday 06 April 2008 08:11, Sam Clemens wrote:

Rodney Baker wrote:

...

...

...

You can easily clone home:

$ su - # change to root password: # type root password $ cd /newhome # or where ever you want to copy /home to. $ (cd /home && tar cvSf - . ) | tar xvSf -

It's probably a good idea to include the tar option that preserves maximal file attributes: -p, --same-permissions, --preserve-permissions extract all protection information And if you don't want all the source files to have their access time updated, include "--atime-preserve": --atime-preserve don't change access times on dumped files If there are active mount points within the source hierarchy and you want to limit the transfered files to those on the same file system as the starting point, use "-l" / "--one-file-system": -l, --one-file-system stay in local file system when creating an archive

...

...

...

Thanks, Sam.

Please, call him Aaron.

Don't thank me...thank SGI

I originally learned that 1-liner trick from the SGI man page for the tar command.

Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-04-06 at 11:11 -0400, Sam Clemens wrote:

...

Don't thank me...thank SGI

I originally learned that 1-liner trick from the SGI man page for the tar command.

It was also here:

/usr/share/doc/howto/en/txt/Hard-Disk-Upgrade.gz

but it was removed:

Previous versions of the Mini How-To stated that you could also use tar to copy the disk, but this method was found to have a bug. There are of course many other ways to copy the disks, but these three are the simplest, quickest, and most reliable.

However, it doesn't say what bug was that.

Randall put his finger on it... The method I listed failed to include flags for preserving permissions (-p), access time (--atime-preserve) and staying within the filesystem (-l). Removing it is rather shortsighted...the editor should have just included the appropriate flags. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-04-06 at 12:19 -0400, Sam Clemens wrote:

...

...

It was also here:

/usr/share/doc/howto/en/txt/Hard-Disk-Upgrade.gz

but it was removed:

Previous versions of the Mini How-To stated that you could also use tar to copy the disk, but this method was found to have a bug. There are of course many other ways to copy the disks, but these three are the simplest, quickest, and most reliable.

However, it doesn't say what bug was that.

Randall put his finger on it...

The method I listed failed to include flags for preserving permissions (-p), access time (--atime-preserve) and staying within the filesystem (-l).

Removing it is rather shortsighted...the editor should have just included the appropriate flags.

It is not as simple as that.

If a different set of options corrected the problem they found, they would have said so and write up the correct encantation. But no, they said it was a bug.

It has to be some bug, then, probably corrected since, or maybe not. I can't say unless they say what the bug was.

If it was an actual bug, then tar would be completely broken, and not fit for use under any circumstance. The editor was just lazy... or, giving him the benefit of the doubt, didn't realize that these flags had been created and were now available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-04-06 at 12:39 -0400, Sam Clemens wrote:

...

...

It is not as simple as that.

If a different set of options corrected the problem they found, they would have said so and write up the correct encantation. But no, they said it was a bug.

It has to be some bug, then, probably corrected since, or maybe not. I can't say unless they say what the bug was.

If it was an actual bug, then tar would be completely broken, and not fit for use under any circumstance.

If he says "bug" then I have to trust him and think it was a bug. A bug doesn't have to affect all uses of a program.

But what would be broken that ONLY hurts that particular command pipeline? writing to stdout instead of a regular file??? That's merely a change of a file descriptor, which would mean that all of tar is broken. Same goes for reading from stdin instead of a regular file. That's one of the big breakthroughs of the Unix concept, totally unheard of at the time...to use the same semantics for writing to a disk file or to print on the screen or to feed to another program... or to send to some other thing... Either tar reads and writes acceptable data, or it doesn't.

I know the current kernel we use has bugs... I know some of them. Is the kernel unfit for use under any circumstance, then?

Tar is such a basic resource that it's either trustworthy, or it is not.

...

The editor was just lazy... or, giving him the benefit of the doubt, didn't realize that these flags had been created and were now available.

I'll grant him laziness, for not specifying the bug.

-- 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 2008-04-06 at 17:32 -0700, Randall R Schulz wrote:

On Sunday 06 April 2008 09:02, Carlos E. R. wrote:

...

...

It was also here:

/usr/share/doc/howto/en/txt/Hard-Disk-Upgrade.gz

It's still there on my 10.3 installation.

The howto, of course. What is not is the tar method. I might find it in one of my old suse cds.

...

but it was removed:

Previous versions of the Mini How-To stated that you could also use tar to copy the disk, but this method was found to have a bug. ...

However, it doesn't say what bug was that.

It does say that the _method_ has a bug, not that _tar_ has a bug.

Whatever :-) But if it was the method, then it could be changed. If they removed the tar method from the howto it must be because the bug could not be bypassed by changing the comand line.

It is lamentable that no further elucidation of the shortcoming is indicated.

That's right. I'd like to know what exactly was the problem. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH+W8WtTMYHG2NR9URAul0AJ0Zx0791x86c27/i/fn8MswBMegyACgiS8Q eCLFBDh5x8vBaz+ODN3+/m8= =vrN8 -----END PGP SIGNATURE----- -- 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 2008-04-07 at 08:06 +0200, jdd sur free wrote:

Carlos E. R. a écrit :

...

That's right. I'd like to know what exactly was the problem.

did you ask the HOWTO authors? I don't have the howto on my disk but one can read it here http://tldp.org/HOWTO/Hard-Disk-Upgrade/index.html

there are two e-mail for authors contact, and the howto is from year 2000, this is not new.

Perhaps...

jdd NB: anyway, why don't you use cp -a???

Because I prefer rsync ;-) One advantage is that if you stop the process and repeat for whatever reason, it will not rewrite everything, but reuse the already copied content. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH+gPdtTMYHG2NR9URAomzAJ9PPNSQ0XdVti4jLC3Bk+QgPXvspwCeLNy7 khuXgmhvcHBPTmKUY7b6NBU= =OL+M -----END PGP SIGNATURE-----

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-04-06 at 06:38 -0400, Sam Clemens wrote:

...

You can easily clone home:

$ su - # change to root password: # type root password $ cd /newhome # or where ever you want to copy /home to. $ (cd /home && tar cvSf - . ) | tar xvSf -

rsync --archive --acls --xattrs --hard-links --del --stats --human-readable /oldhome /newhome/

add --sparse Or a lot of destination files could take up significantly more disk space than on the old disk drive. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-04-06 at 11:17 -0400, Sam Clemens wrote:

...

...

rsync --archive --acls --xattrs --hard-links --del --stats --human-readable /oldhome /newhome/

add --sparse

Yep, it's possible.

...

Or a lot of destination files could take up significantly more disk space than on the old disk drive.

¿A lot? No, shouldn't be a lot.

It depends on his data. Suppose a program does this: opens a file does an lseek 5000000000 writes one character and closes. That's a sparse file. All but the last character are zeros. In the above example, it only takes one block , or maybe a bit more to store...the inode or whatever structure containing mostly block pointers that point to null (indicating that the entire block is full of zeroes), or even indirect or doubly-indirect pointers pointing to null (indicating that all of the blocks which they would be pointed to by the list of direct pointers are full of zeroes). Only the last block actually needs to be recorded on disk. Now... say you do ls -l sparsefile You'll see the size indicated as 500000000001 but if you do ls -s sparsefile you'll see that it only takes up one or a couple blocks. of disk space. Now do cat < sparsefile > sparseback ls -l sparse* both files will have the same byte counts. ls -s sparse* sparsefile will still be the original size sparseback will use up millions of blocks cp --sparse=always sparsefile sparseback ls -l sparse* and ls -s sparse* will now indicate that sparse-back is both the same size, AND the same amount of disk space He might have no sparse files..or he might run some application which creates many. Who knows unless we know every app that he runs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2008/04/06 01:22 (GMT-0500) JB2 apparently typed:

On Sat 05 April 08, JB2 wrote:

...

One of my hdd's has finally croaked (SMART said it was hardware....made all kinds of wacky noises too).

...

My main hdd is 80GB and an ide, the new drive is sata 160GB. I got the new drive to replace my main hdd, so I can move the old main one and make it my backup drive.

...

The new hdd is SATA. Will it mess anything up to have an SATA drive and an ide drive on my system like this?

Thanks for all the answers everyone! I feel comfortable about it now. As Felix said though in his post, trying to clone what I have now onto the new drive is a little too iffy for me, so it looks like I'll have to put /home on a DVD and start from scratch (the only reason I hate and dread doing it though is because with dial-up it all takes so darn long...oh well).

After sleeping, then rereading the original post, and my answer, and other answers, I see I should have waited until after sleeping to write. :-( For what you want to do, simply: 1-replace PATA device with SATA device 2-install, but don't create any users yet 3-add PATA back 4-ensure SATA is the first drive in the BIOS boot order 5-boot SATA 6-clone contents of old /home to new /home 7-create user account(s) to match the uid/gids of /home All the above presumes you do not have multiple PATA HDs in system before adding SATA. In your original post it isn't entirely clear how many PATA are installed. It seems to indicate both more than one and only one. If you originally start with more than one PATA, disregard this post, or disconnect all PATA drives before beginning to follow the above instructions. Alternatively, due to your dialup connection limitation, you could go ahead and try cloning if you don't have more than 14 partitions per disk, but that will require more detailed guidance from here, and more details of your current configuration, including a list of all PATA and what is on them. -- "Either the constitution controls the judges, or the judges rewrite the constitution." Judge Robert Bork Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, Apr 6, 2008 at 11:07 AM, Sam Clemens wrote:

No. Drivers are assigned and used on a disk by disk basis, not on a system-wide basis.

I have a tower which has had as many as 5 different types of disks in it.

Single ended SCSI CD Low Voltage Differential SCSI Hard disks ATAPI CD/DVD IDE hard disks SATA hard disks.

Every disk performed exactly as you would expect it to do so.

My Dell Precision 610 has an 80MB/s 9GB SCSI, a SATA 400GB, 2 DVD-RWs on IDE, and USB storage and network storage attached with no issues as well. I had a PATA drive in at for a while as well. Drive orders can get confused with SCSI and SATA because they use the same sd*, and they are usually assigned by the order that they are installed on the PCI bus. So, if you are using a SCSI card in PCI2 and add a SATA in PCI1, the SATA drive can become sda and push the SCSI drive to sdb. that can cause kernel panics during boot if the SCSI drive was supposed to be sda and had been bumped. I wish they had used a different drive type for SATA, even tho it's basically like SCSI anyway. Oh well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-04-06 at 11:39 -0400, Larry Stotler wrote:

...

that can cause kernel panics during boot if the SCSI drive was supposed to be sda and had been bumped. I wish they had used a different drive type for SATA, even tho it's basically like SCSI anyway. Oh well.

SATA can hook up to a SAS (serial attached SCSI) controller, but SCSI has a larger command set. Basically, this current method can be convenient in some circumstances (replacing SATA disks with SAS disks) ...and annoying in many others (when you really do want to differentiate between your SCSI disks and your non-SCSI disks.... plus the new ridiculously low partition limit being blindly applied to both. The kernel devs must have been on drugs the month they merged that in without doing some basic sanity checking (is this a real SCSI disk, or a SATA disk?... figure it out by probing the hardware with the sg (generic scsi) device, and then choose a real device (SCSI or SATA) accordingly. ARG!!! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org