iSCSI FileIO is using struct file that serves it as block level
device via iSCSI technology:
http://en.wikipedia.org/wiki/ISCSI
Thanks, I know ISCSI very well. But what is "iSCSI FileIO" ? The above
sounds like it's an iscsi target, is that correct?
Yes, it is iSCSI target that is served for another server. The FileIO
serves a file as iSCSI target.
There are RAID level 6 unit on the Areca RAID controller (1680). On
the unit is created a volume group. In the volume group we have
several logical volumes. The iSCSI FileIO volume is mounted and the
file (lun) is served via SCST target as iSCSI LUN.
We have checked RAM with memtest+ and verified RAID unit health and
no issues were found.
I still can't make any sense of the actual setups.
The above seems to be the backend storage. Then there's SCST somewhere
in which is in a out of tree kernel module. And then you use XFS
somewhere. Please provide a full description of the setup.
So once again. We have created a RAID unit level 6. On the top of the
unit there is an LVM architecture, I mean a volume group that contains
logical volumes. The logical volume is formatted with XFS and it
contains one big file that takes almost all of the space on the LV.
There is some free space left in order to be able expand the LV and FS
in the future. The LV is mounted and the file is served as iSCSI target.
The iSCSI Initiator (MS Initiator from Windows 2k3) connects to iSCSI
target. The iSCSI disk is formatted with the NTFS.
But we believe the problem is with the XFS. With unknown reason we are
not able to mount the LV and after running xfs_repair the file is
missing from the LV. Do you have any ideas how we can try to fix the
broken XFS?
Cheers
Slawek
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
