I just noticed that after adding the mount entry to /etc/fstab and rebooting the server, it didn't boot up. I have to remove that entry and only then the server was booting.
Sir i have one question: Suppose we have shared a 5gb lun from our iscsi server to one of our node, and from that node we save some data so technically that data will be stored in the iscsi server right? So is there any way we can see the data from our iscsi server as well??
@@NehraClasses yes i understood that,but in this scenario where im using lun storage and if my node gets faulty and i need to retrive the data how am i going to do that???plz help
When you share a LUN (Logical Unit Number) from your iSCSI server to a node, the node sees this LUN as a local disk. Any data saved on this LUN by the node is indeed stored on the iSCSI server. However, the iSCSI server itself does not directly understand or display the file system and data structures that the node creates on the LUN. To view or interact with the data on the iSCSI server, you would generally have to use tools and techniques that can understand the file system used by the node. Here are some approaches: Mount the LUN on the iSCSI Server: If the iSCSI server is capable of mounting the LUN, you could mount it and then view the data. This requires the iSCSI server to support the file system used by the node. For example, if the node uses an ext4 file system, the iSCSI server must be able to mount ext4 file systems. Use File System Tools: You can use tools like guestmount (from libguestfs) to mount and interact with disk images. This is useful if the iSCSI server runs a different OS or doesn’t support direct mounting. Network File System (NFS): If your iSCSI server also supports NFS, you could export the LUN via NFS, and then mount this NFS share on another system that supports the node’s file system. This way, you can indirectly access the data. Snapshot and Mount: Some advanced iSCSI servers (especially enterprise-grade storage solutions) offer snapshot features. You could create a snapshot of the LUN and then mount the snapshot on a different system that understands the file system used by the node. Check iSCSI Server Documentation: Some iSCSI servers have built-in tools or interfaces to browse or manage the data on LUNs. Consult the documentation of your specific iSCSI server for any such features. Here’s a basic example of how you might mount a LUN on a Linux-based iSCSI server: Discover the iSCSI target on the iSCSI server: iscsiadm -m discovery -t st -p Login to the iSCSI target: iscsiadm -m node --login Find the device name of the LUN (it will be something like /dev/sdX). Create a mount point and mount the LUN: mkdir /mnt/iscsi_lun mount /dev/sdX /mnt/iscsi_lun Now you can navigate to /mnt/iscsi_lun to see the data. Make sure to unmount and logout from the iSCSI target when done: umount /mnt/iscsi_lun iscsiadm -m node --logout Note: Directly mounting and accessing the LUN from the iSCSI server can lead to file system corruption if the LUN is concurrently accessed by multiple systems without proper coordination. Use appropriate locking mechanisms or ensure exclusive access.
Sir, I have created A iscsi target On centos . * After I create iscsi target I give access from two client, Client-1 , Client-2. I successfully connect and mount volume booth client There is no issue to connect. ( Booth client and server is on Centos ) But when I update or create file or folder on the mounted volume from client -1 it transfer done but when I see same volume from client -2 there is empty, there is no file or folder. Then I tried to send some file of folder from client -2 it's transfer fine, but I can't see those file from client-1 that I send from client -2, Still see old file that was I sent from Client-1. That means client-1 can not see client-2's file or folder and client-2 can not see cient-1's file or folder. would you like to help me please about this?
Very Helpful. Worked exactly the way explained in the video. Thanks.
Thanks a lot
Very good steps sir
Very Helpful and well explained.
thank you sir.....so so much...helpfullll
You're welcome
on centos7 target server iscsi disk is missing after reboot, what to do??
please contact us in our telegram group.
Hello sir. Very nice
Thanks
thank u so much good sir
Thank You so much sir !
Excellent lab it is very helpful to me
Thanks
I just noticed that after adding the mount entry to /etc/fstab and rebooting the server, it didn't boot up. I have to remove that entry and only then the server was booting.
awesome sir
professor I am very happy to learn a lot
HOW to Configure Challenge-Handshake Authentication Protocol?
love this video thanks for sharing
Thanks
Sir i have one question:
Suppose we have shared a 5gb lun from our iscsi server to one of our node, and from that node we save some data so technically that data will be stored in the iscsi server right? So is there any way we can see the data from our iscsi server as well??
Use nfs share for that purpose.
@@NehraClasses yes i understood that,but in this scenario where im using lun storage and if my node gets faulty and i need to retrive the data how am i going to do that???plz help
@@NehraClasses kindly guide me
When you share a LUN (Logical Unit Number) from your iSCSI server to a node, the node sees this LUN as a local disk. Any data saved on this LUN by the node is indeed stored on the iSCSI server. However, the iSCSI server itself does not directly understand or display the file system and data structures that the node creates on the LUN.
To view or interact with the data on the iSCSI server, you would generally have to use tools and techniques that can understand the file system used by the node. Here are some approaches:
Mount the LUN on the iSCSI Server: If the iSCSI server is capable of mounting the LUN, you could mount it and then view the data. This requires the iSCSI server to support the file system used by the node. For example, if the node uses an ext4 file system, the iSCSI server must be able to mount ext4 file systems.
Use File System Tools: You can use tools like guestmount (from libguestfs) to mount and interact with disk images. This is useful if the iSCSI server runs a different OS or doesn’t support direct mounting.
Network File System (NFS): If your iSCSI server also supports NFS, you could export the LUN via NFS, and then mount this NFS share on another system that supports the node’s file system. This way, you can indirectly access the data.
Snapshot and Mount: Some advanced iSCSI servers (especially enterprise-grade storage solutions) offer snapshot features. You could create a snapshot of the LUN and then mount the snapshot on a different system that understands the file system used by the node.
Check iSCSI Server Documentation: Some iSCSI servers have built-in tools or interfaces to browse or manage the data on LUNs. Consult the documentation of your specific iSCSI server for any such features.
Here’s a basic example of how you might mount a LUN on a Linux-based iSCSI server:
Discover the iSCSI target on the iSCSI server:
iscsiadm -m discovery -t st -p
Login to the iSCSI target:
iscsiadm -m node --login
Find the device name of the LUN (it will be something like /dev/sdX).
Create a mount point and mount the LUN:
mkdir /mnt/iscsi_lun
mount /dev/sdX /mnt/iscsi_lun
Now you can navigate to /mnt/iscsi_lun to see the data.
Make sure to unmount and logout from the iSCSI target when done:
umount /mnt/iscsi_lun
iscsiadm -m node --logout
Note: Directly mounting and accessing the LUN from the iSCSI server can lead to file system corruption if the LUN is concurrently accessed by multiple systems without proper coordination. Use appropriate locking mechanisms or ensure exclusive access.
@@NehraClasses thankyou so much
Hello, Just need to confirm:
Can we treat this FS as a Raw FS and can be used in cluster service?
Yes we can, I have shown that in cluster configuration video as well.
Sir,
I have created A iscsi target On centos .
* After I create iscsi target I give access from two client, Client-1 , Client-2. I successfully connect and mount volume booth client There is no issue to connect. ( Booth client and server is on Centos )
But when I update or create file or folder on the mounted volume from client -1 it transfer done but when I see same volume from client -2 there is empty, there is no file or folder. Then I tried to send some file of folder from client -2 it's transfer fine, but I can't see those file from client-1 that I send from client -2, Still see old file that was I sent from Client-1. That means client-1 can not see client-2's file or folder and client-2 can not see cient-1's file or folder.
would you like to help me please about this?
Did they hacked you at the beginning ??