On Tue, Nov 29, 2022 at 11:47:47AM -0500, Benjamin Coddington wrote:
> On 29 Nov 2022, at 9:02, Christoph Hellwig wrote:
>
> > Hmm. Having to set a flag to not accidentally corrupt per-task
> > state seems a bit fragile. Wouldn't it make sense to find a way to opt
> > into the feature only for
On Tue, Nov 29, 2022 at 03:02:42PM +0100, Christoph Hellwig wrote:
> Hmm. Having to set a flag to not accidentally corrupt per-task
> state seems a bit fragile. Wouldn't it make sense to find a way to opt
> into the feature only for sockets created from the syscall layer?
That's something I
Le mardi 12 mars 2013 23:30:47 UTC+1, Mike Christie a écrit :
On 03/12/2013 08:11 AM, Guillaume wrote:
Hello Mike
On 12 mar, 02:54, Mike Christie micha...@cs.wisc.edu wrote:
On 03/09/2013 05:58 AM, Guillaume wrote:
Hello,
I have a virtual tape library and a iscsi SAN
Le mercredi 13 mars 2013 15:44:04 UTC+1, hare a écrit :
On 03/12/2013 11:30 PM, Mike Christie wrote:
On 03/12/2013 08:11 AM, Guillaume wrote:
Hello Mike
On 12 mar, 02:54, Mike Christie micha...@cs.wisc.edu wrote:
On 03/09/2013 05:58 AM, Guillaume wrote:
Hello,
I have
Hello Mike
On 12 mar, 02:54, Mike Christie micha...@cs.wisc.edu wrote:
On 03/09/2013 05:58 AM, Guillaume wrote:
Hello,
I have a virtual tape library and a iscsi SAN. All have multiple
ethernet interfaces, This will ressult in multiples sessions to the
targets.So I wonder if I must use
Hello,
If I want to use 802.3ad I must have multiple links to the same switch. For
redundancy purposes, each host is connected to two separated networks (like
a dual fabric in FC).
Regards,
Guillaume
Le dimanche 10 mars 2013 03:07:01 UTC+1, Mark Lehrer a écrit :
I have a virtual tape
the output of iscsiadm -m session : the lines of
output begins by @IP:3260,n where n is an integer. Is this number a
priority level in some way, or does it only distinguish multiple sessions
to the same iqn ?
Regards,
Guillaume
--
You received this message because you are subscribed
Le mercredi 25 avril 2012 06:15:55 UTC+2, Mike Christie a écrit :
Data digests are not supported in centos/rhel 5. You should get a
different error though. You should not get that stack trace below. If
you guys are getting a stack trace like below I will try to do some more
debugging.
Hello,
I did have the same problem from Redhat EL5 CentOS. The same target
is not problematic with Ubuntu and Win7 initiators.
I discovered that my problem come from the DATA CRC32C. When I
deactivate the data digest on the Syno, the Redhat can login to the
target.
I have no problem with header
I have the same problem with Redhat EL5 and CentOS 5 initiators, but not
with Ubuntu or Win7.
The problem arise when I activate data CRC on the Syno. I have no problem
with header CRC.
It seems that the data digest parameter is not supported by RH CentOS.
Le jeudi 8 mars 2012 16:44:03 UTC+1,
10 matches
Mail list logo
