StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
586236
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-02-25T14:43:35.943
FavoriteCount
0
LastActivityDate
2009-02-25T14:43:35.943
LastEditDate
LastEditorUserId
0
OwnerUserId
64079
ParentId
586180
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
dmesg might help. On a system where we do have software raid we see things like: SCSI device sda: 143374744 512-byte hdwr sectors (73408 MB) sda: Write Protect is off sda: Mode Sense: ab 00 10 08 SCSI device sda: write cache: enabled, read cache: enabled, supports DPO and FUA SCSI device sda: 143374744 512-byte hdwr sectors (73408 MB) sda: Write Protect is off sda: Mode Sense: ab 00 10 08 SCSI device sda: write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sda2 sd 0:0:0:0: Attached scsi disk sda SCSI device sdb: 143374744 512-byte hdwr sectors (73408 MB) sdb: Write Protect is off sdb: Mode Sense: ab 00 10 08 SCSI device sdb: write cache: enabled, read cache: enabled, supports DPO and FUA SCSI device sdb: 143374744 512-byte hdwr sectors (73408 MB) sdb: Write Protect is off sdb: Mode Sense: ab 00 10 08 SCSI device sdb: write cache: enabled, read cache: enabled, supports DPO and FUA sdb: sdb1 sdb2 sd 0:0:1:0: Attached scsi disk sdb A bit later we see: md: md0 stopped. md: bind md: bind md: raid0 personality registered for level 0 md0: setting max_sectors to 512, segment boundary to 131071 raid0: looking at sda2 raid0: comparing sda2(63296000) with sda2(63296000) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sdb2 raid0: comparing sdb2(63296000) with sda2(63296000) raid0: EQUAL raid0: FINAL 1 zones raid0: done. raid0 : md_size is 126592000 blocks. raid0 : conf->hash_spacing is 126592000 blocks. raid0 : nb_zone is 1. raid0 : Allocating 4 bytes for hash. and a df shows: Filesystem Size Used Avail Use% Mounted on /dev/sda1 7.8G 3.3G 4.2G 45% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/md0 117G 77G 35G 69% /scratch So part of sda and all of sdb have been bound as one raid volume. What you have could be one disk, or it could be hardware raid. dmesg should give you some clues. It is always possible that it is a hardware raid controller that just looks like a single sata (or scsi) drive. Ie, our systems with fiber channel raid arrays, linux only sees a single device, and you control the raid portion and disk assignment via connecting to the fiber raid array directly.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODiscovering linux disk configurations from the command line
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBruce ONeel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COSCSI device sdb: 584843264 512-byte hdwr sectors (299440 MB) SCSI device sdb: 584843264 512-byte hdwr sectors (299440 MB) sdb: asking for cache data failed sdb: assuming drive cache: write through sdb: sdb1 Attached scsi disk sdb at scsi0, channel 2, id 1, lun 0 so.. not raided?
 singulars
 PostPostId
 PO
 UserUserId
 USchillitom
2. COIt could be hardware raided, but, it doesn't look like it's raided with software.
 singulars
 PostPostId
 PO
 UserUserId
 USBruce ONeel

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.