sda and sdb seem mirrored but not sure
by plisken from LinuxQuestions.org on (#5CDVH)
I'm not entirely sure how to explain this or if this is the best forum but I'll try my best.
I've come across something that is confusing me and that is it would seem that sda and sdb are mirrored on a server I'm working on but not really sure.
So, to begin with I was using fsarchiver when I noticed this and thought I'd try and dig a bit deeper.
when I ran cfdisk /dev/sda and cfdisk /dev/sdb they are identical, so I used fsarchiver on both (to be safe) and of course the file sizes of the archives were the same too so wondering how this could be.
I have always assumed that if the drivers were in a mirrored raid, then we would physically see only the one drive, at least that's been my experience so...
df gives us;
Code:Filesystem Size Used Avail Use% Mounted on
rootfs 46G 3.7G 40G 9% /
udev 10M 0 10M 0% /dev
tmpfs 2.4G 508K 2.4G 1% /run
/dev/disk/by-uuid/a68992e0-70a8-4f94-9923-ed5292dfda30 46G 3.7G 40G 9% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 11G 0 11G 0% /run/shm
/dev/sdb9 523G 8.6G 488G 2% /dl
/dev/sdb5 46G 11G 34G 24% /home
/dev/sdb6 92G 1.9G 86G 3% /pcli
/dev/sdb7 92G 1.7G 86G 2% /usr
/dev/sdb8 92G 2.9G 85G 4% /var
23.128.30.24:/volume1/BACKUP/HN_BACKUPS 25T 22T 2.8T 89% /media/temp_nas
/dev/sdb5 46G 11G 34G 24% /tmp/fsa/20201221-162251-00fdisk -l gives us;
Code:Disk /dev/sda: 1000.2 GB, 1000171331584 bytes
255 heads, 63 sectors/track, 121597 cylinders, total 1953459632 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disk identifier: 0x0000bf04
Device Boot Start End Blocks Id System
/dev/sda1 * 512 97656319 48827904 83 Linux
/dev/sda2 97656830 1894531583 898437377 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda3 1894531584 1953459199 29463808 82 Linux swap / Solaris
/dev/sda5 97656832 195312639 48827904 83 Linux
/dev/sda6 195313152 390625279 97656064 83 Linux
/dev/sda7 390625792 585937919 97656064 83 Linux
/dev/sda8 585938432 781250559 97656064 83 Linux
/dev/sda9 781251072 1894531583 556640256 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000171331584 bytes
255 heads, 63 sectors/track, 121597 cylinders, total 1953459632 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disk identifier: 0x0000bf04
Device Boot Start End Blocks Id System
/dev/sdb1 * 512 97656319 48827904 83 Linux
/dev/sdb2 97656830 1894531583 898437377 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sdb3 1894531584 1953459199 29463808 82 Linux swap / Solaris
/dev/sdb5 97656832 195312639 48827904 83 Linux
/dev/sdb6 195313152 390625279 97656064 83 Linux
/dev/sdb7 390625792 585937919 97656064 83 Linux
/dev/sdb8 585938432 781250559 97656064 83 Linux
/dev/sdb9 781251072 1894531583 556640256 83 LinuxThoughts and comments greatly appreciated.
I've come across something that is confusing me and that is it would seem that sda and sdb are mirrored on a server I'm working on but not really sure.
So, to begin with I was using fsarchiver when I noticed this and thought I'd try and dig a bit deeper.
when I ran cfdisk /dev/sda and cfdisk /dev/sdb they are identical, so I used fsarchiver on both (to be safe) and of course the file sizes of the archives were the same too so wondering how this could be.
I have always assumed that if the drivers were in a mirrored raid, then we would physically see only the one drive, at least that's been my experience so...
df gives us;
Code:Filesystem Size Used Avail Use% Mounted on
rootfs 46G 3.7G 40G 9% /
udev 10M 0 10M 0% /dev
tmpfs 2.4G 508K 2.4G 1% /run
/dev/disk/by-uuid/a68992e0-70a8-4f94-9923-ed5292dfda30 46G 3.7G 40G 9% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 11G 0 11G 0% /run/shm
/dev/sdb9 523G 8.6G 488G 2% /dl
/dev/sdb5 46G 11G 34G 24% /home
/dev/sdb6 92G 1.9G 86G 3% /pcli
/dev/sdb7 92G 1.7G 86G 2% /usr
/dev/sdb8 92G 2.9G 85G 4% /var
23.128.30.24:/volume1/BACKUP/HN_BACKUPS 25T 22T 2.8T 89% /media/temp_nas
/dev/sdb5 46G 11G 34G 24% /tmp/fsa/20201221-162251-00fdisk -l gives us;
Code:Disk /dev/sda: 1000.2 GB, 1000171331584 bytes
255 heads, 63 sectors/track, 121597 cylinders, total 1953459632 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disk identifier: 0x0000bf04
Device Boot Start End Blocks Id System
/dev/sda1 * 512 97656319 48827904 83 Linux
/dev/sda2 97656830 1894531583 898437377 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda3 1894531584 1953459199 29463808 82 Linux swap / Solaris
/dev/sda5 97656832 195312639 48827904 83 Linux
/dev/sda6 195313152 390625279 97656064 83 Linux
/dev/sda7 390625792 585937919 97656064 83 Linux
/dev/sda8 585938432 781250559 97656064 83 Linux
/dev/sda9 781251072 1894531583 556640256 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000171331584 bytes
255 heads, 63 sectors/track, 121597 cylinders, total 1953459632 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disk identifier: 0x0000bf04
Device Boot Start End Blocks Id System
/dev/sdb1 * 512 97656319 48827904 83 Linux
/dev/sdb2 97656830 1894531583 898437377 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sdb3 1894531584 1953459199 29463808 82 Linux swap / Solaris
/dev/sdb5 97656832 195312639 48827904 83 Linux
/dev/sdb6 195313152 390625279 97656064 83 Linux
/dev/sdb7 390625792 585937919 97656064 83 Linux
/dev/sdb8 585938432 781250559 97656064 83 Linux
/dev/sdb9 781251072 1894531583 556640256 83 LinuxThoughts and comments greatly appreciated.