From: "G.R." <firemeteor@users.sourceforge.net>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0
Date: Sun, 26 Dec 2021 02:06:55 +0800 [thread overview]
Message-ID: <CAKhsbWarxwi_n3NAr81op_apyN69itUrv7f1k1ZJ6=gXuFXtGA@mail.gmail.com> (raw)
In-Reply-To: <CAKhsbWZ4Xyy_7Xp4F3YWNsrBXdh4AkiQx4__7qUTd4AJiu-6bg@mail.gmail.com>
> > Thanks. I've raised this on freensd-net for advice [0]. IMO netfront
> > shouldn't receive an mbuf that crosses a page boundary, but if that's
> > indeed a legit mbuf I will figure out the best way to handle it.
> >
> > I have a clumsy patch (below) that might solve this, if you want to
> > give it a try.
>
> Applied the patch and it worked like a charm!
> Thank you so much for your quick help!
> Wish you a wonderful holiday!
I may have said too quickly...
With the patch I can attach the iscsi disk and neither the dom0 nor
the NAS domU complains this time.
But when I attempt to mount the attached disk it reports I/O errors randomly.
By randomly I mean different disks behave differently...
I don't see any error logs from kernels this time.
(most of the iscsi disks are NTFS FS and mounted through the user mode
fuse library)
But since I have a local backup copy of the image, I can confirm that
mounting that backup image does not result in any I/O error.
Looks like something is still broken here...
next prev parent reply other threads:[~2021-12-25 18:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 18:35 Possible bug? DOM-U network stopped working after fatal error reported in DOM0 G.R.
2021-12-19 6:10 ` Juergen Gross
2021-12-19 17:31 ` G.R.
2021-12-20 17:13 ` G.R.
2021-12-21 13:50 ` Roger Pau Monné
2021-12-21 18:19 ` G.R.
2021-12-21 19:12 ` Roger Pau Monné
2021-12-23 15:49 ` G.R.
2021-12-24 11:24 ` Roger Pau Monné
2021-12-25 16:39 ` G.R.
2021-12-25 18:06 ` G.R. [this message]
2021-12-27 19:04 ` Roger Pau Monné
[not found] ` <CAKhsbWY5=vENgwgq3NV44KSZQgpOPY=33CMSZo=jweAcRDjBwg@mail.gmail.com>
2021-12-29 8:32 ` Roger Pau Monné
2021-12-29 9:13 ` G.R.
2021-12-29 10:27 ` Roger Pau Monné
2021-12-29 19:07 ` Roger Pau Monné
2021-12-30 15:12 ` G.R.
2021-12-30 18:51 ` Roger Pau Monné
2021-12-31 14:47 ` G.R.
2022-01-04 10:25 ` Roger Pau Monné
2022-01-04 16:05 ` G.R.
2022-01-05 14:33 ` Roger Pau Monné
2022-01-07 17:14 ` G.R.
2022-01-10 14:53 ` Roger Pau Monné
2022-01-11 14:24 ` G.R.
2022-10-30 16:36 ` G.R.
2022-11-03 6:58 ` Paul Leiber
2022-11-03 12:22 ` Roger Pau Monné
2022-12-14 6:16 ` G.R.
2024-01-09 11:13 ` Niklas Hallqvist
2024-01-09 13:53 ` Roger Pau Monné
2024-01-19 15:51 ` G.R.
2021-12-20 13:51 ` Roger Pau Monné
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='CAKhsbWarxwi_n3NAr81op_apyN69itUrv7f1k1ZJ6=gXuFXtGA@mail.gmail.com' \
--to=firemeteor@users.sourceforge.net \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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.