ci4...@gmail.com (Chavdar Ivanov) writes:
>> istgt is the iSCSI server.
>> The crash is about the in-kernel iscsi initiator.
>The first sentence in the first message in the thread says 'I can see
>some panics on a server that exports iSCSI volumes (istgt on
>a CCB device' (CCB later corrected as
Thanks! I didn't realise it is both a target and an initiator.
Apart from a few tests years ago, I don't remember using the in-kernel
iSCSI target (which was flaky for me at the time - the initiators who
were using it didn't reattach after a reboot). As far as the
initiator, I've only tried it
Chavdar Ivanov a écrit :
> On Sat, 12 Jun 2021 at 19:30, Michael van Elst wrote:
>>
>> On Sat, Jun 12, 2021 at 05:02:11PM +0100, Chavdar Ivanov wrote:
>>
>>> Not that this has any connection to your problem, but I'd nevertheless
>>> add my 5c about istgt - I have been serving zvols for perhaps
On Sat, 12 Jun 2021 at 19:30, Michael van Elst wrote:
>
> On Sat, Jun 12, 2021 at 05:02:11PM +0100, Chavdar Ivanov wrote:
>
> > Not that this has any connection to your problem, but I'd nevertheless
> > add my 5c about istgt - I have been serving zvols for perhaps one year
> > now under -current
On Sat, Jun 12, 2021 at 05:02:11PM +0100, Chavdar Ivanov wrote:
> Not that this has any connection to your problem, but I'd nevertheless
> add my 5c about istgt - I have been serving zvols for perhaps one year
> now under -current without any problems.
istgt is the iSCSI server.
The crash is
On Sat, 12 Jun 2021 at 14:19, BERTRAND Joël wrote:
>
> Michael van Elst a écrit :
> > joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
> >
> >>> If you have a version of the kernel with debug symbols, you could
> >>> use addr2line to identify the instruction that caused the
Michael van Elst a écrit :
> joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
>
>>> If you have a version of the kernel with debug symbols, you could
>>> use addr2line to identify the instruction that caused the uvm_fault
>>> at address 0x802280cc. Without debug symbols
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
>> If you have a version of the kernel with debug symbols, you could
>> use addr2line to identify the instruction that caused the uvm_fault
>> at address 0x802280cc. Without debug symbols it is not
>> that easy.
> I
Michael van Elst a écrit :
> joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
>
>> Hello,
>
>> I can see some panics on a server that exports iSCSI volumes (istgt on
>> a CCB device) to some workstations. dmesg always contains this kind of
>> backtrace :
>
> That
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
> Hello,
> I can see some panics on a server that exports iSCSI volumes (istgt on
>a CCB device) to some workstations. dmesg always contains this kind of
>backtrace :
That would be on the workstation that uses the
10 matches
Mail list logo
