>>> Lee Duncan schrieb am 14.12.2016 um 20:18 in
Nachricht <8286a277-f7fe-4c7d-a944-40034a0b5...@gmail.com>:
> On Dec 12, 2016, at 5:46 AM, Dave partridge
wrote:
>>
>> I just ran a Wireshark capture on the target system of the iSCSI session
for
__bitwise__ used to mean "yes, please enable sparse checks
unconditionally", but now that we dropped __CHECK_ENDIAN__
__bitwise is exactly the same.
There aren't many users, replace it by __bitwise everywhere.
Signed-off-by: Michael S. Tsirkin
---
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
> instantly on the first
On 12/09/2016 03:33 PM, Mike Christie wrote:
> On 12/08/2016 10:55 AM, andrew.patter...@hpe.com wrote:
>> I am trying to get iSCSI boot working on a debian-based system
>> using built-in uEFI iSCSI initiator firmware and broadcom
>> NICs (bnx2x).
>>
>> The debian initramfs uses the ibft support in
I am trying to get iSCSI boot working on a debian-based system
using built-in uEFI iSCSI initiator firmware and broadcom
NICs (bnx2x).
The debian initramfs uses the ibft support in iscsistart to log
into the root volume. The initramfs script uses iscsistart -N to
bring up the NICs before logging
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
instantly on the first mount of an iscsi device:
[ 159.372704] XFS (sdb): EXPERIMENTAL reverse
On Dec 12, 2016, at 5:46 AM, Dave partridge wrote:
>
> I just ran a Wireshark capture on the target system of the iSCSI session for
> a Windows initiator connecting the tape and then issuing an FSF. I then did
> the same for the Ubuntu open-iscsi initiator.
>
> The