I'm able to find existing WWIDEMC LUN id by using INQ utility but for Hitachi it is not possible. Do you guys have any idea to find the LUN's. For Solaris and AIX I have no issues and the problem is only with Linux end.

I have a partition that's NFS-mounted from a Netapp SAN. I can create files in that partition, and I can chown those files to another user, any user, even root. How am I able to do so? I thought the kernel would prevent such a thing. I have done this again and again today, using multiple user IDs on the file. I cannot do this in /tmp or in my home directory, which is locally-mounted. I've never seen this behaviour before. Also, I note that setcap/getcap are not found on this machine. I have checked my shell's capabilities and they are all 0's: $ echo $$ 15007 $ cat /proc/15007/task/15007/status Name: bash State: S (sleeping) SleepAVG: 98% Tgid: 15007 Pid: 15007 PPid: 14988 TracerPid: 0 Uid: 71579 71579 71579 71579 Gid: 10000 10000 10000 10000 FDSize: 256 Groups: 9000 10000 10001 10013 10018 10420 24611 36021 ... CapInh: 0000000000000000 CapPrm: 0000000000000000 CapEff: 0000000000000000 I am on a Red Hat 5.3 virtual machine: $ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.3 (Tikanga) Running an old kernel: $ uname -r 2.6.18-274.7.1.el5 The NFS mount uses defaults: $ cat /etc/fstab ... mynetapp00:/home /mnt/home nfs defaults 0 0 For user authentication, we're using Windows Active Directory with ldap on the Linux side: $ grep passwd /etc/nsswitch.conf passwd: files ldap I'm able to do anthing as sudo: User mikes may run the following commands on this host: (ALL) ALL because I'm one of the ADMINS (contents of /etc/sudoers): User_Alias ADMINS = fred, tom, mikes ADMINS ALL=(ALL) ALL ...But I don't know how that's germaine, because sudo isn't involved. In any event, I was able to create a file and give it my ownership as a user "john" who's not found in /etc/sudoers: # grep john /etc/sudoers # su - john $ touch /mnt/home/blah $ chown mikes /mnt/home/blah $ ls -l /mnt/home/blah -rwxrwxrwx 1 mikes DomainUsers 0 Oct 23 19:45 /mnt/home/blah ...and chown is not aliased (but we knew that, because if chown was an alias or some other program, then I would be able to change ownership in /tmp too): $ alias alias l.='ls -d .* --color=tty' alias ll='ls -l --color=tty' alias ls='ls --color=tty' alias vi='vim' alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde' $ which chown /bin/chown P.S. I'm not kidding: $ id uid=71579(mikes) gid=10000(DomainUsers) $ touch /mnt/home/blah $ chown john /mnt/home/blah $ ls -l /mnt/home/blah -rwxrwxrwx 1 john DomainUsers 0 Oct 23 19:04 /mnt/home/blah $ id john uid=37554(john) gid=10000(DomainUsers) $ chmod 755 /mnt/home/blah chmod: changing permissions of `/mnt/home/blah': Operation not permitted $ rm /mnt/home/blah $ ls -l /mnt/home/blah ls: /mnt/home/blah: No such file or directory $ touch /tmp/blah $ chown john /tmp/blah chown: changing ownership of `/tmp/blah': Operation not permitted

We have RedHat servers. How can we determine if a physical Linux server is booting from SAN or has a local disk? Which files can indicate this? I ask because we need to perform some configuration only on the servers that boot from SAN.

I had created physical volume earlier i.e. /backup, /ndasdb, /processor, /latro. Don't know what exactly happened, but /ndasdb is not showing in any of this output result: Pvdisplay, Vgdisplay, and lvdisplay. rest 3 are showing. I can see the lun in multipath -ll (ndasdb is there) I tried to recreate it with pvcreate /dev/mapper/ndasdb but its gives me this error: WARNING: gfs2 signature detected on /dev/mapper/ndasdb at offset 65536. Wipe it? [y/n]: n Aborted wiping of gfs2. 1 existing signature left on the device. Is it true if I do yes it will delete my all data? Is there anyway to bring my drive back without loosing any data?

I am setting up multipaths for Veritas backup on SAN storage. I noticed that lsblk shows duplicate disks, which is quite confusing. For example, both sdc and sdd represent the same disk, and similarly, sde and sdf represent the same device. sdc 8:32 0 50G 0 disk ├─sdc1 8:33 0 50G 0 part └─san69 253:10 0 50G 0 mpath └─san69p1 253:11 0 50G 0 part sdd 8:48 0 50G 0 disk ├─sdd1 8:49 0 50G 0 part └─san69 253:10 0 50G 0 mpath └─san69p1 253:11 0 50G 0 part sde 8:64 0 69G 0 disk ├─sde1 8:65 0 69G 0 part └─mpathb 253:12 0 69G 0 mpath └─mpathb1 253:13 0 69G 0 part /mnt sdf 8:80 0 69G 0 disk ├─sdf1 8:81 0 69G 0 part └─mpathb 253:12 0 69G 0 mpath └─mpathb1 253:13 0 69G 0 part /mnt multipath -ll output is as follow mpathb (360050763808106804800000000000001) dm-12 IBM,2145 size=69G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=active | `- 11:0:1:1 sde 8:64 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 11:0:3:1 sdf 8:80 active ready running san69 (360050763808106804800000000000000) dm-10 IBM,2145 size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=enabled | `- 11:0:3:0 sdc 8:32 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 11:0:1:0 sdd 8:48 active ready running

I'm confused about the actual internal workings of a file system. The question is about file storage vs block storage. From what I understand, the difference is in the level at which we access data: File storage at a file level and block storage at block level. My question is: Does file storage also ultimately divide the file in to chunks and store it again on individual blocks? And so the difference is really in who is responsible for combining these chunks to form the file? In case of block storage this is done by the OS on that block server and in case of file storage it is the OS with help of the file system? Follow up: In case of block storage, how does the OS keep track of the various chunks of the same file without using a file system then?

I have a lab consisting of 3 machines connected with 2 10gbe links on 2 segregated networks. Each device has 100tb in block storage connected to it. I want to use ATA over Ethernet to create a storage cluster which can be accessed from all the machines at one time. I want to do this from both the client and initiators at the same time. I want to be able to mount the target file system on multiple initiators. I do not need to write to the filesystem from multiple systems at once, but I do want to read from the file system from many at once. I have thought about creating cache devices, though i would like to avoid this if possible. I know this is a rather complex problem, but I feel like i'm missing something, as it seems like what I want should be possible. I have been playing around but have not come up with a good plan on how to do this. I've setup a target using vblade, and accessed that from a separate system; however I'm unable to access it from the host, if I access it from 2 initiators at once then it seems to become corrupted of course. Additionally, I am not sure what filesystem i can use which will allow what I want without becoming corrupted. I tried btrfs, xfs, zfs... I am thinking maybe I am going about it wrong, so thought I'd write this post and see if anyone can share some ideas. I think i need to use GFS but I haven't been able to get it setup correctly. **So my question is if it possible to access the same disk from two systems at the same time using AOE?** *relevant stuff:* - I do not want to use nfs, samba, ssh, or any of these options. - Security is not a concern it is on a closed internal air-gapped network. - Yes I've searched but it is hard to find relevant info. - the systems are each have 2 10gbe links, one for tcp/ip, one for ata over ethernet. - I'm open to suggestions, but I don't especially want to have to code a new solution, and want to stick with open source software. - I apologize in advance for my poorly written question.

I have an older redhat (5) server that needs to have 9 array filesystems moved to a new array. I'm seeking some assistance on the best way of doing this and how the process works. The data is being copied directly as an array level copy. I have been given the 9 LUNids (WWN) from the existing server and I see them in the output of multipath -ll. I also have the LUNids on the new storage that correspond to the old. I am unsure how to migrate to the new storage. I don't fully understand the role of LVM commands like pvscan. I think the procedure is going to be to quiesce the array filesystems and unmount them and remove from /etc/fstab so they don't try to be mounted on boot. Then shutdown server and connect the new array LUNids, then boot. At this stage I expect to see the new LUNids from multipath -ll. Is this correct? And as I've not specified any custom device naming I will also see device names of the form mpathX for each? I know that each PV has a UUID, as does a VG and LV. Is that the key information that allows LVM to reconstruct each PV and consequently the volume groups and logical volumes such that it all contains the same data? That is, the PV of /dev/mapper/mpath24 from one of the new LUNid disks will be the same data because its been identified by the UUID that is on that disk? Will this just work? After the reboot and multipath has discovered and enumerated the paths and devices (and updated /etc/multipath/bindings) will LVM simply start, automatically interrogate the disks and essentially, Just Work? So I can go ahead and mount the filesystems just as before? If not what steps do I need to take? Do I need to run pv/vg/lv scan? It would be helpful to know what happens when multipath starts up, and what happens when LVM starts. Lastly, is it possible to avoid a reboot, or is it safest to do that for orderliness of the processes? If I could do this without reboot what steps would I need to take after umounting filesystems and attaching the new LUNids? Is there are sequence of multipath and subsequent LVM commands that would do the same thing as a reboot process? and any additional steps I need in either case? Thank you. r.

I have a ProLiant server with a HBA card (2 ports). $ ls /sys/class/fc_host host2 host3 and also I have a 20T SAN storage that is connected to San switch via those ports. Is it possible to monitor my HBA ports and find the amount of data that went through those HBA ports? For example: I had 2GB data IO from host2 in 1 second.

I have a Debian 9 running. It has a SSD connected as well as a fibrechannel link to a SAN storage. As far I see both are visible as /dev/sdX devices. How can I find out what is the disk and what is the storage? Where is the storage configured in the system?

I saw an IBM San Storage and at Host alias creation page they can show you available host (client) initiators wwn's to choose. And I wonder how they can find client initiator wwn's from storage? I think they should be using a discover method for taking this information from SAN switch via fc but how? If we simplify the question I'm the Storage System as you can see at below. And I want to discover available initiator port wwn number via FC port. Do you know anything about this?

I have a scenario where my shared storage is available at SAN (Storage Area Network). The SAN is available through Fiber Channel. I am installing some oracle product and want to use storage from SAN only. The problem I am facing regarding 'mount' of location from SAN to my Linux machine. Attached the screenshot.

We presume to have a faulty cable that connects the SAN to a direct I/O LDOM. This is a snippet of the error when running iostat -En c5t60060E8007C50E000030C50E00001067d0 Soft Errors: 0 Hard Errors: 696633 Transport Errors: 704386 Vendor: HITACHI Product: OPEN-V Revision: 8001 Serial No: 504463 Size: 214.75GB Media Error: 0 Device Not Ready: 0 No Device: 6 Recoverable: 0 Illegal Request: 1 Predictive Failure Analysis: 0 What does No Device: 6 mean here?

I have a hba card with two ports (port 0) and (port 1) and I want to know how can obtaining using OS the info to mapping the wwn that I can see using fcinfo hba-port command to a port of the hba card. For example: If I have a WWN ending on xxxx890B, see that wwn is on port 0 of the hba card.

I have a scenario where I am trying to mount SAN storage to my linux machine. My environment details are- 1. Oracle VM manager for VM creation 2. Fiber Channel HP3PAR SAN storage attached as physical disk to my VM 3. Oracle Linux version -OEL 7.4 Below steps I have been doing as earlier worked smoothly but not now- 1. Login as root user on VM Running 2. fdisk utility to check attached disks fdisk -l It shows 2 disks /dev/xvdb & /dev/xvdc where /dev/xvdc appeared after attaching the SAN storage to VM. 3. Applying mount command to mount /dec/xvdc on location /u01/oracle/config where /u01/oracle/config is empty mount /dev/xvdc /u01/oracle/config 4. After this the command screen cursor just blinks and nothing happens. Further I have checked whether the mount was successful, no it is not. Running the command 'df -h' and 'mount' doesn't shows the storage was mounted to requested location.

Actually I want to know how can I see the Luns presented using a HBA WWN. The view that I want is something like this: LUN (on the server side like /dev/rdsk/...) | WWN (from the server) | Paths (the paths that connect my hba wwn from the server to the hba's wwn of the storage)

I have a scenario where I have to use SAN storage for my Oracle Database installation single node production setup and need to keep Database configuration files on SAN. I am using Oracle VM manager to manage my Oracle Linux 7.5. After attaching a SAN storage of capacity 1.2TB it was available & shown using 'fdisk -l' command. I have gone though different file systems viz ext2, ext3, ext4, xfs, ocfs2 etc and was little bit confused that time regarding which one should I use. However I have formatted the disk of 1.2TB using command 'mkfs.ext2 -b 4096 /dev/xvdc'. Everything is working fine and I am able to mount the disk /dev/xvc on my Linux Machine and have configured my database at SAN. The question is whether it is fine to go with this file system i.e. ext2 in current production environment or should I plan to migrate it as ext3/ext4/xfs etc. If required then what could be the step wise process for migration? Thanks Kumar

I am running RHEL 6.x in my production and booting from local disk which is actually RAID 1 configured from BIOS. (IBM Blade Center H) I wish to migrate this to SAN disk and perform SAN booting. This Post in a way resembles to my problem. I have /boot and /boot/efi as partition and rest of remaining space allocated to vg-lvm and OS FS is mapped. /boot and /boot/efi is of size 1 GB each. I am planning to clone /boot and /boot/efi on san disk with dd command. May be I need to install grub on SAN disk as well. and then I will perform pvmove and migrate OS FS on to SAN disk. Is this the correct way to migrate OS disk to another ? Let's assume this is just DISK to DISK migration where the size of disk is different and exclude the SAN part.

My storage administrator assigned LUNS for a RHEL 5.10 Server. Now when I run /sbin/scsi_id -g -u -s /block/sdN, it shows: 360060160c8803500183327ae00a2e711 Now I want to see the exact name, just like the storage administrator assigned, such as: DB2_LUN_1 What am I missing? The back end storage from EMC.

I want to configure multipath such that it ignores all the internal disks and only sees SAN Luns. Any idea how can I achieve that? Basically I want to filter out all the internal disks like IDE, SAS backend etc except for SAN Luns. -- Using find_multipaths is not an option for me as I want to use multipath even when single path to a SAN Lun is present. -- Black listing based on device(vendor/model), wwid etc is also not an option as it is possible that I can have internal drive(s) as well as SAN LUN from the same vendor. -- I tried black listing using properties but could not find any property that will distinguish between SAN Luns vs internal disks. Any thoughts? I am new to the Linux internals. Thank you