On Wed, Dec 21, 2016 at 09:46:37PM -0800, Linus Torvalds wrote:
> On Wed, Dec 21, 2016 at 9:13 PM, Dave Chinner <da...@fromorbit.com> wrote:
> >
> > There may be deeper issues. I just started running scalability tests
> > (e.g. 16-way fsmark create tests)
On Thu, Dec 22, 2016 at 04:13:22PM +1100, Dave Chinner wrote:
> On Wed, Dec 21, 2016 at 04:13:03PM -0800, Chris Leech wrote:
> > On Wed, Dec 21, 2016 at 03:19:15PM -0800, Linus Torvalds wrote:
> > > Hi,
> > >
> > > On Wed, Dec 21, 2016 at 2:16 PM, Dave
On Wed, Dec 21, 2016 at 04:13:03PM -0800, Chris Leech wrote:
> On Wed, Dec 21, 2016 at 03:19:15PM -0800, Linus Torvalds wrote:
> > Hi,
> >
> > On Wed, Dec 21, 2016 at 2:16 PM, Dave Chinner <da...@fromorbit.com> wrote:
> > > On Fri, Dec 16, 2016 at
report, so I'm not really sure what's going on here anyway.
http://www.gossamer-threads.com/lists/linux/kernel/2587485
Cheers,
Dave.
--
Dave Chinner
da...@fromorbit.com
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscrib
On Fri, Dec 16, 2016 at 10:59:06AM -0800, Chris Leech wrote:
> Thanks Dave,
>
> I'm hitting a bug at scatterlist.h:140 before I even get any iSCSI
> modules loaded (virtio block) so there's something else going on in the
> current merge window. I'll keep an eye on it and ma
On Thu, Dec 15, 2016 at 09:24:11AM +1100, Dave Chinner wrote:
> Hi folks,
>
> Just updated my test boxes from 4.9 to a current Linus 4.10 merge
> window kernel to test the XFS merge I am preparing for Linus.
> Unfortunately, all my test VMs using iscsi failed pretty much
> inst
00 00 00 00 e9 ad fe ff ff 48 8b 7b 30 e8 da e7 ca
ff 8b 53 10 44 89 ee 48 89 df 2b 53 14 48 89 43 30 c7 43 40 00 00 00 00 <8b
[ 160.300674] RIP: iscsi_tcp_segment_done+0x20d/0x2e0 RSP: c9083c38
[ 160.301584] CR2: 000c
Known problem, or something new?
Cheers,
Dave.
--
D
knowledge of the iSCSI protocols).
The Ubuntu/open-iscsi capture has all sorts of odd stuff like logins being
sent to the target every 15 seconds whle the FSF is being processed.
Definitely borked I think.
Do any of the open-iscsi folk watch this forum or am I talking to myself?
Dave
On Sunday
Ubuntu 16.04.1 LTS with kernel 4.8.13. Connected to target drive over 1GB
ethernet. Drive is HP Ultrium 460 (Ultrium 2), firmware is F63D - which is
latest).
Target is served by Starwind V8 running on Windows 10 x64
Dave
On Saturday, December 10, 2016 at 10:38:43 PM UTC, The Lee-Man wrote
ing that the problem relates to iSCSI timeouts for tape devices.
Please can you guide me in baby steps what I need to do to resolve this problem.
Thanks
Dave
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this g
IIRC, LVM was wonky when I tried to fix something similar to this.
Assuming you only want the partitions on sda, sdb, sdc and the
multipath devices, try:
filter = [ a|/dev/dm-*|, a|/dev/sda[0-9]|, a|/dev/sdb[0-9]|, a|/
dev/sdc[0-9]|, r|.*| ]
--
Dave
On May 3, 2:45 pm, James Hammer jham
And delete the lvm cache before the scan, if you haven't already.
--
Dave
On May 3, 8:33 pm, dave dave-goo...@dubkat.com wrote:
IIRC, LVM was wonky when I tried to fix something similar to this.
Assuming you only want the partitions on sda, sdb, sdc and the
multipath devices, try:
filter
Hi -
My name is Dave Kroon, and I am support engineer for DTS Inc. I would like to
know if open-scsi supports 'persistant reservation'?
Hope to hear from you all.
Thanks
Dave
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post
the modules and daemon of 2.0-871 from open-
iscsi.org, or should I just install the iscsi-initiator-utils from the
yum repo of CentOS 5.4? How can I make sure I have the most stable
iscsi modules and daemon?
Thanks,
Dave
--
You received this message because you are subscribed to the Google Groups
open
the connection is recovered and then resume operation like
nothing happened.
Thanks in advance,
Dave
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi
Can anyone tell me why the SCSI layer says the device is not ready
when iscsiadm reports it is logged in?
Can I manually online the device? How should I recover from here?
Is this a known problem, and has it been fixed in newer open-iscsi
versions?
Mar 18 18:21:33 eq1-vz2 kernel:
On Mar 19, 10:56 am, Mike Christie micha...@cs.wisc.edu wrote:
dave wrote:
Can anyone tell me why the SCSI layer says the device is not ready
when iscsiadm reports it is logged in?
Can I manually online the device? How should I recover from here?
You can do
echo running /sys/block
17 matches
Mail list logo
