Stability of FILEIO as backing store?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I have a weird issue with using a file as backing store with a Win2016 server as initiator. 

Very often if I reboot the Linux server the disk image becomes corrupt so that Windows cannot even detect the gpt partition table on it. It can happen even if I shut down the Windows machine before I reboot the Linux server.

Initially I thought I would be write cache. But I've disabled that with no benefit to this problem. 

There are no errors in dmesg except initially when loading the target. Perhaps I'm doing wrong when rebooting? 


[   71.583665] dev[0000000064b6f5d8]: Unable to change SE Device alua_support: alua_support has fixed value
[   71.583676] dev[0000000064b6f5d8]: Unable to change SE Device alua_support: alua_support has fixed value
[   71.583837] ignoring deprecated emulate_dpo attribute
[   71.583874] ignoring deprecated emulate_fua_read attribute
[   71.584553] dev[0000000064b6f5d8]: Unable to change SE Device pgr_support: pgr_support has fixed value
[   71.584561] dev[0000000064b6f5d8]: Unable to change SE Device pgr_support: pgr_support has fixed value


The LIO target is running Fedora 33 Server with two Seagate Exos 10TB in Btrfs RAID-1 mode.

Are there any debugging options that would help?

Thanks for any advice.

~Forza



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux