Date: Tue, 10 Apr 2018 06:28:55 +0800 From: Julian Elischer <julian@freebsd.org> To: Kyle Evans <kevans@freebsd.org>, Peter Holm <peter@holm.cc> Cc: Michael Dexter <editor@callfortesting.org>, FreeBSD Current <freebsd-current@freebsd.org>, "O. Hartmann" <ohartmann@walstatt.org> Subject: Re: g_handleattr: md0 bio_length 24 len 31 -> EFAULT Message-ID: <0181f13e-7451-7d13-6605-9116fdb387c8@freebsd.org> In-Reply-To: <CACNAnaFXzTf8_RqLx7SO76Z0EAf6vi9JHi7LZyZvb=d1gBRm9A@mail.gmail.com> References: <20180324103615.7b88c33f@thor.intern.walstatt.dynvpn.de> <cdee528f-2aaa-72d5-80db-d77743693b22@callfortesting.org> <20180408105321.GA55435@x2.osted.lan> <CACNAnaFXzTf8_RqLx7SO76Z0EAf6vi9JHi7LZyZvb=d1gBRm9A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/4/18 10:48 pm, Kyle Evans wrote: > On Sun, Apr 8, 2018 at 5:53 AM, Peter Holm <peter@holm.cc> wrote: >> On Sun, Apr 08, 2018 at 02:36:08AM -0700, Michael Dexter wrote: >>> On 3/24/18 2:35 AM, O. Hartmann wrote: >>>> Writing out memory (md) backed images of UFS2 filesystems (NanoBSD images, created via >>>> the classical manual way, no makefs), my recent CURRENT system dumps the >>>> console full of these error messages: >>>> >>>> g_handleattr: md0 bio_length 24 len 31 -> EFAULT >>>> >>>> I do not know what they are supposed to mean and I'd like to ask whether someone could >>>> shed some light on this. >>> I am seeing this on the the latest snapshot when attempting to run >>> option_survey.sh which creates an md-attached disk image. >>> >>> Anyone else seeing this? >>> >>> Michael >> Yes, I have: >> >> [pho@freefall ~/public_html/stress/log]$ grep -a g_handleattr: `ls -rt` >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> numa025.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> kostik1104.txt:g_handleattr: md10 bio_length 24 len 31 -> EFAULT >> [pho@freefall ~/public_html/stress/log]$ >> > FYI- this should be fixed by r332070. > > Thanks, > > Kyle Evans > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > so I think current has other issues I want to avoid can I just pull that commit and have have svn know how to upgrade past it later?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0181f13e-7451-7d13-6605-9116fdb387c8>