Hot answers tagged

4

More convenient way is to use lsscsi utility. From documentation about FC: For FC devices (logical units), the '--transport' option will show the port name and the port identifier instead of the SCSI INQUIRY "strings". For example: $ lsscsi -g [3:0:0:0] enclosu HP A6255A HP04 - /dev/sg3 [3:0:1:0] disk HP 36.4G ...


3

You can not. From my experience as storage and linux admin I can tell you, DB2_LUN_1 is alias on storage level. You can confirm the unique id from storage admin which is similar to 360060160c8803500183327ae00a2e711 (well most of the part). if you are using dm-multipath drivers then you can set alias in your /etc/multipath.conf file. multipath { wwid ...


3

I found an informal article making the same comparison, which matches the rough impression I had. The article also shows multi-pathing to survive failure of an FC switch, or of one of the cables into a big SAN, as @Sobrique mentions. SCSI doesn’t take kindly to dropped commands. It’s a bit of a misconception that SCSI can’t tolerate a lost command. It ...


2

It might be one for ServerFault. But you're quite correct. Fiber Channel doesn't have the same protection mechanisms as TCP. It's more like UDP in that regard (although that's a bit of a weak analogy) and for many of the same reasons - for some applications, TCP is bad solution because of those reliability mechanisms - your stream can 'stall' for a ...


2

Do not user ext2 or ext3 if you are planning to use files that are larger than about 40kB, as those filesystems use block tables and more than 10 blocks need indirect block tables. This slows random access to the file data, requiring multiples block reads for one file block. ext4 uses extents (i.e. the file blocks are listed as "starting with block number x ...


1

On a Debian 9 or similar fairly modern distribution, you might use the lsblk command like this: lsblk -o +HCTL,TRAN,WWN The TRAN field will identify the transport method used, but may be blank. But the first number of the HCTL quadlet will indicate the number of the host adapter providing access to this device: if a corresponding /sys/class/fc_host/host&...


1

Before mounting the SAN storage on your virtual machine, you'll need to present the storage to the VM(s). There are two ways to do it: A. present the entire 1250 GiB LUN as a single device to a single VM or to a cooperating cluster of VMs. or B. initialize the LUN as Oracle VM storage repository, then use that repository in creating any number virtual ...


1

Yes, chown is the purview of the kernel, but remember that the NetApp is beyond the kernel’s arm reach.  For local filesystems, the kernel translates user I/O requests into local hardware I/O operations (on the storage device).  For remote (e.g., NFS) filesystems, the kernel translates user I/O requests into network communications, asking / telling the ...


1

You can try something like: check the major and the minor numbers for this device: # ls -l /dev/sd* brw-rw---- 1 root disk 8, 0 May 15 12:58 /dev/sda then go to directory /sys/dev/block/8:0/device where 8:0 represent above major and minor number and get the content of file model # cat model VBOX HARDDISK P.S. This is for RHEL, on Debian the path maybe ...


1

discover all HBAs using fcinfo hba-port to filter wwid fcinfo hba-port | awk '/HBA Port WWN/ { print $4 ; } ' | while read wwid do echo fcinfo remote-port -sl -p $wwid fcinfo remote-port -sl -p $wwid done that will give you which equipement is connected to your local HBA. to configure switch zone use Remote Port WWN: field. (please note you can only ...


1

fcinfo may give the information you require. Example: # fcinfo remote-port -s -p 10000000c993b528 Remote Port WWN: 5006016239a01db6 Active FC4 Types: SCSI SCSI Target: yes Node WWN: 50060160b9a01db6 LUN: 0 Vendor: DGC Product: LUNZ OS Device Name: /dev/rdsk/c2t5006016239A01DB6d0s2 LUN: 1 ...


1

Based on the comment string, it appears that editing /usr/lib/systemd/system/postgresql.service with After=local-fs.target fixed the situation. The hint for me was the message: postgresql-check-db-dir: "/var/lib/pgsql/data" is missing or empty which implied that postgres was attempting to start before /var was mounted. Adding the after restriction forces ...


1

usual try ioscan -e -C fc ioscan -fnC fc if 11iV3 fcinfo (can't remember syntax)


Only top voted, non community-wiki answers of a minimum length are eligible