Hey, is it possible to get device disk name by id/wwn (Example in Linux : /dev/disk/by-id/wwn-0x5000c500a4b222a3) ?

Purpose - to get persistent known device name across controllers and reboots, when device name is changing.

vetal: paste.dilos.org/?fb09bfd4c29347fb#j…m274PanqCiRtGAaKN3DpPdWIPrP3z+DsAQ=

denk: In some cases that is not true and device name is not exactly as LUN. Logical Unit id: 0x5002538b7210dfa0, but device name is /dev/dsk/c6t5002538B7210DFA2d0

Question was about to have device name w/o controller number, exactly as wwwn, LUN, serial.

Is it possible to configure ?

I'm not sure you can configure it manually, only clean device tree file to reorder nodes

denk: In linux: LU WWN Device Id: 5 000c50 0a4b222a3, and device name is: /dev/disk/by-id/wwn-0x5000c500a4b222a3

I.e. exactly as LU WWN

you can find something like that in /devices directory

vetal: ls -l /devices/scsi_vhci

in theory you can find a corresponded device by reading the soft link in /dev/dsk directory

hello all, I hit / is full on my smartos after my machine is reboot, I think is some core dump or some large file used / file syste, anyone could help how to find that? and thant I can delete the unused file

tozhu: df -h /

is it a ramdisk?

yes， but there are a lot of dataset under /zones

zones is a pool

total: 313.28M used: 309.98M avail: 3.30M

don’t know which file used the space

it could be a "deleted" file, where some process has a reference to a file which does not have a corresponded name in any directory

tmpfile() returns an opened file descriptor without a name

so, if a process uses it, it's too hard to find it

denk: thanks for the advice

denk: Ho success, device with Logical Unit id: 0x5002538b7210dfa0, is not in /devices/scsi_vhci

denk: However it has Transport protocol: SAS (SPL-4)

denk: It is in /devices/pci@54,0/pci8086,2030@0/pci1000,30e0@0/iport@ff/disk@w5002538b7210dfa2,0, but again

Instead of be as WWN 5002538b7210dfa0, it has 5002538b7210dfa2

Yeah, it is very close to 5002538b7210dfa0, but is bigger by 2 :)

vetal: once I saw such behaviour of the system when sas cables were connected incorrect

it was with an external jbod connected to two servers

denk: What do mean by incorrect?

connector A must be plugged to a hole B, but it was plugged to hole A

as result we saw sas-loop

run "fmstat 1", column ev_recv must be near 0

denk: Yes, it is 0

vetal: reddit.com/r/sysadmin/comments/17cn…ng_a_external_minisas_connection_to

"Are the cables plugged into the correct cards / the correct ports?"

denk: I don't think that it is that case. Drives are seen, but not exactly with the same WWN. It looks like problem in a driver.

vetal: community.hpe.com/t5/hpe-eva-storag…ong-wwn-being-reported/td-p/3729098

denk: From it 'the first port will ALWAYS end with "2" and the second port with "3"' that explains ending with 2 for 5002538b7210dfa2.

denk: However, that does not bring solution in general, because for LSISAS3008, device name is changed and

denk: Device is Logical Unit id: 0x5000cca04d1a6ba8

denk: But device name is /dev/rdsk/c39t5000CCA04D1A6BA9d0 , and after reboot it becomes /dev/rdsk/c38t5000CCA04D1A6BAAd0

vetal: I have any good ideas, I said what I saw and knew

denk: Even if to wwn 0x5000cca04d1a6ba8 is added "1" to get c39t5000CCA04D1A6BA9, I dont understand why it becomes ending AA after reboot

i.e. c38t5000CCA04D1A6BAA

And It looks like adding 1 or 2 to wwn depends on SAS controller and how get it in general?

I mean algorithm to get proper device name by disk WWN suitable for all SAS controllers.