All of lore.kernel.org
 help / color / mirror / Atom feed
From: Forza <forza@tnonline.net>
To: target-devel@vger.kernel.org
Subject: Stability of FILEIO as backing store?
Date: Thu, 25 Feb 2021 22:36:27 +0100 (GMT+01:00)	[thread overview]
Message-ID: <af031d3.b2327dec.177db1f2641@tnonline.net> (raw)

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

             reply	other threads:[~2021-02-25 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 21:36 Forza [this message]
2021-02-25 22:09 ` Stability of FILEIO as backing store? Chaitanya Kulkarni
2021-02-25 22:20   ` Chaitanya Kulkarni
2021-02-26  3:41 ` michael.christie
2021-02-26  7:19   ` Forza
2021-02-26 16:12     ` Mike Christie
2021-03-01 15:38       ` Forza
2021-03-02 11:22         ` Maurizio Lombardi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=af031d3.b2327dec.177db1f2641@tnonline.net \
    --to=forza@tnonline.net \
    --cc=target-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.