11:43:13 Hey, is it possible to get device disk name by id/wwn (Example in Linux : /dev/disk/by-id/wwn-0x5000c500a4b222a3) ? 11:45:19 Purpose - to get persistent known device name across controllers and reboots, when device name is changing. 11:50:21 vetal: https://paste.dilos.org/?fb09bfd4c29347fb#jVnRB4DZ4m274PanqCiRtGAaKN3DpPdWIPrP3z+DsAQ= 12:07:16 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 12:08:38 Question was about to have device name w/o controller number, exactly as wwwn, LUN, serial. 12:09:05 Is it possible to configure ? 12:11:37 I'm not sure you can configure it manually, only clean device tree file to reorder nodes 12:50:41 denk: In linux: LU WWN Device Id: 5 000c50 0a4b222a3, and device name is: /dev/disk/by-id/wwn-0x5000c500a4b222a3 12:50:58 I.e. exactly as LU WWN 13:07:12 you can find something like that in /devices directory 13:08:10 vetal: ls -l /devices/scsi_vhci 13:09:47 in theory you can find a corresponded device by reading the soft link in /dev/dsk directory 13:12:04 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 13:16:52 tozhu: df -h / 13:17:07 is it a ramdisk? 13:17:35 yes， but there are a lot of dataset under /zones 13:18:07 zones is a pool 13:18:44 total: 313.28M used: 309.98M avail: 3.30M 13:19:04 don’t know which file used the space 13:21:03 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 13:21:54 tmpfile() returns an opened file descriptor without a name 13:22:16 so, if a process uses it, it's too hard to find it 13:25:59 denk: thanks for the advice 13:26:59 denk: Ho success, device with Logical Unit id: 0x5002538b7210dfa0, is not in /devices/scsi_vhci 13:27:13 denk: However it has Transport protocol: SAS (SPL-4) 13:29:17 denk: It is in /devices/pci@54,0/pci8086,2030@0/pci1000,30e0@0/iport@ff/disk@w5002538b7210dfa2,0, but again 13:30:07 Instead of be as WWN 5002538b7210dfa0, it has 5002538b7210dfa2 13:30:44 Yeah, it is very close to 5002538b7210dfa0, but is bigger by 2 :) 13:35:45 vetal: once I saw such behaviour of the system when sas cables were connected incorrect 13:36:27 it was with an external jbod connected to two servers 13:41:55 denk: What do mean by incorrect? 13:43:14 connector A must be plugged to a hole B, but it was plugged to hole A 13:43:27 as result we saw sas-loop 13:44:46 run "fmstat 1", column ev_recv must be near 0 13:47:30 denk: Yes, it is 0 13:56:35 vetal: https://www.reddit.com/r/sysadmin/comments/17cnpu5/troubleshooting_a_external_minisas_connection_to/ 13:57:02 "Are the cables plugged into the correct cards / the correct ports?" 14:05:41 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. 14:22:20 vetal: https://community.hpe.com/t5/hpe-eva-storage/wrong-wwn-being-reported/td-p/3729098 14:35:34 denk: From it 'the first port will ALWAYS end with "2" and the second port with "3"' that explains ending with 2 for 5002538b7210dfa2. 14:43:38 denk: However, that does not bring solution in general, because for LSISAS3008, device name is changed and 14:43:48 denk: Device is Logical Unit id: 0x5000cca04d1a6ba8 14:44:45 denk: But device name is /dev/rdsk/c39t5000CCA04D1A6BA9d0 , and after reboot it becomes /dev/rdsk/c38t5000CCA04D1A6BAAd0 14:46:07 vetal: I have any good ideas, I said what I saw and knew 14:46:16 denk: Even if to wwn 0x5000cca04d1a6ba8 is added "1" to get c39t5000CCA04D1A6BA9, I dont understand why it becomes ending AA after reboot 14:46:29 i.e. c38t5000CCA04D1A6BAA 14:47:20 And It looks like adding 1 or 2 to wwn depends on SAS controller and how get it in general? 14:48:48 I mean algorithm to get proper device name by disk WWN suitable for all SAS controllers.