Nabble - iSCSI Enterprise Target

Re: Compile Errors

2008-10-13T09:31:53Z

Cool thanks for the tip. It is much appreciated.

-----Original Message-----
From: Ross S. W. Walker [mailto:RWalker@...]
Sent: Monday, October 13, 2008 8:46 AM
To: Jeremy Custenborder; Ross Walker
Cc: iscsitarget-devel@...
Subject: RE: [Iscsitarget-devel] Compile Errors

Jeremy Custenborder wrote:
>
> That would make sense to me. Any tips on preventing this from
> happening again?
>

If your on Ubuntu or SLES either use the IET that ships with it or
use the version from Sourceforge, don't install both or a different
kernel module will install through apt/yum which can cause problems...

For iSCSI targets I would try systems that don't change their kernels
very often. You want your targets to act more like appliances then
servers. Something like CentOS or Debian stable if your a debian fan.

You can explore software like DKMS to keep your SourceForge kernel
module up-to-date with your kernel version.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@...
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

From forum: iscsitarget-devel

Re: Compile Errors

2008-10-13T08:46:20Z

Jeremy Custenborder wrote:
>
> That would make sense to me. Any tips on preventing this from
> happening again?
>

If your on Ubuntu or SLES either use the IET that ships with it or
use the version from Sourceforge, don't install both or a different
kernel module will install through apt/yum which can cause problems...

For iSCSI targets I would try systems that don't change their kernels
very often. You want your targets to act more like appliances then
servers. Something like CentOS or Debian stable if your a debian fan.

You can explore software like DKMS to keep your SourceForge kernel
module up-to-date with your kernel version.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@...
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

From forum: iscsitarget-devel

Re: Compile Errors

2008-10-12T22:59:52Z

That would make sense to me. Any tips on preventing this from happening again?

On Sun, Oct 12, 2008 at 10:51 PM, Ross Walker <rswwalker@...> wrote:

>
> On Oct 12, 2008, at 8:14 PM, Jeremy Custenborder wrote:
>
>> Get ready for some weirdness. I decided to update my kernel to 2.6.27,
>> recompiled iscsi-target off trunk, and it is working perfectly again. I
>> cannot repro the issue anymore and everything is working perfectly. Hehe
>> this is totally annoying because I would love to know the exact cause for
>> the problem. The box ran fine for two months on the previous kernel version.
>> Again thanks for your help it was 1000% appreciated.
>>
>> J
>>
>
> Maybe you had the older kernel module creep back after an update?
>
> Make sure the kernel module matches the userland tools.
>
> I don't think we actually store version information in the kernel module. We
> should start compiling it in...
>
> -Ross
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@...
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

From forum: iscsitarget-devel

Re: Compile Errors

2008-10-12T22:51:29Z

On Oct 12, 2008, at 8:14 PM, Jeremy Custenborder wrote:

> Get ready for some weirdness. I decided to update my kernel to
> 2.6.27, recompiled iscsi-target off trunk, and it is working
> perfectly again. I cannot repro the issue anymore and everything is
> working perfectly. Hehe this is totally annoying because I would
> love to know the exact cause for the problem. The box ran fine for
> two months on the previous kernel version. Again thanks for your
> help it was 1000% appreciated.
>
> J
>

Maybe you had the older kernel module creep back after an update?

Make sure the kernel module matches the userland tools.

I don't think we actually store version information in the kernel
module. We should start compiling it in...

-Ross

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@...
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

From forum: iscsitarget-devel

Re: Compile Errors

2008-10-12T18:21:10Z

On Sun, 2008-10-12 at 17:14 -0700, Jeremy Custenborder wrote:
> Get ready for some weirdness. I decided to update my kernel to 2.6.27,
> recompiled iscsi-target off trunk, and it is working perfectly again.
> I cannot repro the issue anymore and everything is working perfectly.
> Hehe this is totally annoying because I would love to know the exact
> cause for the problem. The box ran fine for two months on the previous
> kernel version. Again thanks for your help it was 1000% appreciated.
>
> J

anyway. good news for you... maybe some bugs in other part of the
kernel...

ming

>
>
>
> -----Original Message-----
> From: Ming Zhang [mailto:blackmagic02881@...]
> Sent: Friday, October 10, 2008 6:09 AM
> To: Jeremy Custenborder
> Cc: iscsitarget-devel@...
> Subject: Re: [Iscsitarget-devel] Compile Errors
>
> On Thu, 2008-10-09 at 19:40 -0700, Jeremy Custenborder wrote:
> > On Thu, Oct 9, 2008 at 5:49 PM, Ming Zhang
> <blackmagic02881@...> wrote:
> > > On Thu, 2008-10-09 at 17:39 -0700, Jeremy Custenborder wrote:
> > >> On Thu, Oct 9, 2008 at 4:52 PM, Ming Zhang
> <blackmagic02881@...> wrote:
> > >> > On Thu, 2008-10-09 at 15:41 -0700, Jeremy Custenborder wrote:
> > >> >> no they are on different hardware. A snippit of my config is
> below.
> > >> >> Thanks for the assistance, I really appreciate it. /dev/sda is
> a 6.1TB
> > >> >> disk that is presented by a Highpoint 3522 raid controller.
> > >> >> /root/iscsidisk is a file on a single disk attached to the
> motherboard
> > >> >> of the box. This is also the same drive that the OS is
> installed.
> > >> >> /root/iscsidisk is a sparse file on ext3 that is 500gb in
> size.
> > >> >> /dev/sda1 and /dev/sda2 are 2TB partitions presented directly
> to
> > >> >> iscsi-target
> > >> >>
> > >> >> Target iqn.2008-08.msp.localdomain:volume1
> > >> >> Lun 0 Path=/dev/sda1,Type=blockio
> > >> >> Target iqn.2008-08.msp.localdomain:volume2
> > >> >> Lun 1 Path=/dev/sda2,Type=blockio
> > >> >
> > >> > so these 2 share same raid. raid5? any nvram cache?
> > >>
> > >> correct /dev/sda* is on the same raid controller running raid 6
> across
> > >> 8x1TB drives. The controller has 256MB of cache and each drive
> has
> > >> 32mb of cache. /root/iscsidisk is a sparse file on a regular 1TB
> sata
> > >> disk that also has 32MB of cache.
> > >>
> > >>
> > >> > i guess when lock up, u copy between these 2?
> > >> Correct The problem happened when copying from /dev/sda2
> to /root/iscsidisk.
> > >
> > > reading from raid6, will not be a bottleneck. but writing to a
> sparse
> > > file under ext3 on top of one disk might be slow. though should
> not lead
> > > to lock up.
> > >
> > >>
> > >>
> > >>
> > >> > btw, do you know how to use crash? a linux utility allow u to
> examine
> > >> > kernel lively?
> > >>
> > >> no I'm a little bit of a nub. Can you point me at a tutorial? I
> know
> > >> windows kernel debugging but have never worked with linux kernel
> > >> bugging.
> > >
> > > then give up, this one is not a easy one, especially under ubuntu.
> >
> > nah lets give it a shot. I'm a nub to linux but not development.
> I've
> > got a couple
> > rockstars at the office that can help me out if I get stuck. I'll
> look
> > into getting myself up to speed.
>
> i know you are good at development (via linkedin). actually you should
> be able to figure this out. ;)
>
>
>
> >
> >
> > > btw, ubuntu split the kernel log to different files
> under /var/log.
> > > could you reproduce the bug and run dmesg and see if anything.
> > >
> > > check meminfo to see if out of memory. enable nmi and see if any
> dead
> > > lock.
> >
> > I'll give it a try
> >
> > > when u got that lock up. the machine just hangs and have to cold
> reset,
> > > or eventually it came back.
> >
> > when it hangs it totally hangs and I have to power cycle the
> hardware.
>
> try to prepare your system with NMI enabled and with kdump enabled.
> once
> this happen, force a crash dump and we can check which thread stuck.
> because of deadlock, or because of OOM.
>
>
> i am not familiar with ubuntu, otherwise can give your exact
> instruction.
>
> >
> >
> > >>
> > >>
> > >> >> Target iqn.2008-08.msp.localdomain:sparsedisk
> > >> >> Lun 2 Path=/root/iscsidisk,Type=fileio
> > >> >>
> > >> >>
> > >> >> On Thu, Oct 9, 2008 at 2:38 PM, Ming Zhang
> <blackmagic02881@...> wrote:
> > >> >> > On Thu, 2008-10-09 at 14:32 -0700, Jeremy Custenborder
> wrote:
> > >> >> >> yep it's 64 bit. I've watched it under load and all seems
> pretty well.
> > >> >> >> These errors have happened when copying data over night.
> That might
> > >> >> >> make things interesting getting the perfect slice of data.
> I had this
> > >> >> >> configuration working pretty well based off trunk from a
> while ago.
> > >> >> >> Like an idiot I did not back up that source and now I'm on
> the quest
> > >> >> >> for the stable version again. Trunk had locked up on me
> before that is
> > >> >> >> why I tried 162.
> > >> >> >
> > >> >> >>
> > >> >> >> The scenario that hung looked like this. I remember seeing
> the NIC on
> > >> >> >> the XP box hitting 30 - 40 % of 1gbps. I'll try to repro
> the problem
> > >> >> >> when I get home tonight.
> > >> >> >>
> > >> >> >> iscsi-target box --Move Data (Read / Delete)--> XP Box
> ini 2.07 --
> > >> >> >> Write--> same iscsi-target box.
> > >> >> >
> > >> >> > do these 2 target share same RAID?
> > >> >> >
> > >> >> >
> > >> >> >>
> > >> >> >> On Thu, Oct 9, 2008 at 2:11 PM, Ming Zhang
> <blackmagic02881@...> wrote:
> > >> >> >> > btw, when iet hangs, meminfo at that moment is useful as
> well.
> > >> >> >> >
> > >> >> >> > also because we can not ssh into the box, a test case
> allow u to quickly
> > >> >> >> > reproduce it will be helpful as well.
> > >> >> >> >
> > >> >> >> > i assumed it is a 64bit box, right?
> > >> >> >> >
> > >> >> >> >
> > >> >> >> > On Thu, 2008-10-09 at 13:53 -0700, Jeremy Custenborder
> wrote:
> > >> >> >> >> Oh sorry. 6GB.
> > >> >> >> >>
> > >> >> >> >> cat /proc/meminfo
> > >> >> >> >> MemTotal: 6133692 kB
> > >> >> >> >> MemFree: 5331500 kB
> > >> >> >> >> Buffers: 65408 kB
> > >> >> >> >> Cached: 603384 kB
> > >> >> >> >> SwapCached: 0 kB
> > >> >> >> >> Active: 140008 kB
> > >> >> >> >> Inactive: 566232 kB
> > >> >> >> >> SwapTotal: 17928500 kB
> > >> >> >> >> SwapFree: 17928500 kB
> > >> >> >> >> Dirty: 0 kB
> > >> >> >> >> Writeback: 0 kB
> > >> >> >> >> AnonPages: 37516 kB
> > >> >> >> >> Mapped: 19288 kB
> > >> >> >> >> Slab: 49284 kB
> > >> >> >> >> SReclaimable: 40160 kB
> > >> >> >> >> SUnreclaim: 9124 kB
> > >> >> >> >> PageTables: 3888 kB
> > >> >> >> >> NFS_Unstable: 0 kB
> > >> >> >> >> Bounce: 0 kB
> > >> >> >> >> WritebackTmp: 0 kB
> > >> >> >> >> CommitLimit: 20995344 kB
> > >> >> >> >> Committed_AS: 71480 kB
> > >> >> >> >> VmallocTotal: 34359738367 kB
> > >> >> >> >> VmallocUsed: 302992 kB
> > >> >> >> >> VmallocChunk: 34359434691 kB
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >> >> On Thu, Oct 9, 2008 at 1:47 PM, Ming Zhang
> <blackmagic02881@...> wrote:
> > >> >> >> >> > On Thu, 2008-10-09 at 13:38 -0700, Jeremy Custenborder
> wrote:
> > >> >> >> >> >> Below is my hardware information. I will try to repro
> my problems with
> > >> >> >> >> >> against trunk tonight. Sorry about the CC. I was
> planning on adding
> > >> >> >> >> >> the list after I got more specific instructions. I
> took a look at
> > >> >> >> >> >> var/log/messages but did not really write down the
> time or see
> > >> >> >> >> >> anything out of the ordinary.
> > >> >> >> >> >
> > >> >> >> >> >
> > >> >> >> >> > RAM size?
> > >> >> >> >> >
> > >> >> >> >> >
> > >> >> >> >> > not a problem. when this happen, try to use top to see
> which process
> > >> >> >> >> > take most cpu. and see if disconnect ini can let the
> problem go away.
> > >> >> >> >> > otherwise it is a hard lock up.
> > >> >> >> >> >
> > >> >> >> >> >
> > >> >> >> >> >>
> > >> >> >> >> >> Intel Dual core
> > >> >> >> >> >> processor : 0
> > >> >> >> >> >> vendor_id : GenuineIntel
> > >> >> >> >> >> cpu family : 6
> > >> >> >> >> >> model : 23
> > >> >> >> >> >> model name : Intel(R) Core(TM)2 Duo CPU
> E7200 @ 2.53GHz
> > >> >> >> >> >> stepping : 6
> > >> >> >> >> >> cpu MHz : 2533.213
> > >> >> >> >> >> cache size : 3072 KB
> > >> >> >> >> >> physical id : 0
> > >> >> >> >> >> siblings : 2
> > >> >> >> >> >> jeremy@server:~$ head /proc/version
> > >> >> >> >> >> Linux version 2.6.26.3 (root@server) (gcc version
> 4.2.3 (Ubuntu
> > >> >> >> >> >> 4.2.3-2ubuntu7)) #1 SMP Sat Aug 23 04:32:51 PDT 2008
> > >> >> >> >> >> jeremy@server:~$ head /proc/swap
> > >> >> >> >> >> head: cannot open `/proc/swap' for reading: No such
> file or directory
> > >> >> >> >> >> jeremy@server:~$ head /proc/swaphead /proc/partitions
> > >> >> >> >> >> jeremy@server:~$ head /proc/partitions
> > >> >> >> >> >> major minor #blocks name
> > >> >> >> >> >>
> > >> >> >> >> >> 8 0 5860098048 sda
> > >> >> >> >> >> 8 1 1953126441 sda1
> > >> >> >> >> >> 8 2 1953600390 sda2
> > >> >> >> >> >> 8 16 976762584 sdb
> > >> >> >> >> >> 8 17 96847821 sdb1
> > >> >> >> >> >> 8 18 1 sdb2
> > >> >> >> >> >> 8 21 6040408 sdb5
> > >> >> >> >> >> 8 22 855943137 sdb6
> > >> >> >> >> >> jeremy@server:~$
> > >> >> >> >> >>
> > >> >> >> >> >> processor : 0
> > >> >> >> >> >> vendor_id : GenuineIntel
> > >> >> >> >> >> cpu family : 6
> > >> >> >> >> >> model : 23
> > >> >> >> >> >> model name : Intel(R) Core(TM)2 Duo CPU
> E7200 @ 2.53GHz
> > >> >> >> >> >> stepping : 6
> > >> >> >> >> >> cpu MHz : 2533.213
> > >> >> >> >> >> cache size : 3072 KB
> > >> >> >> >> >> physical id : 0
> > >> >> >> >> >> siblings : 2
> > >> >> >> >> >>
> > >> >> >> >> >>
> > >> >> >> >> >> Linux version 2.6.26.3 (root@server) (gcc version
> 4.2.3 (Ubuntu
> > >> >> >> >> >> 4.2.3-2ubuntu7)) #1 SMP Sat Aug 23 04:32:51 PDT 2008
> > >> >> >> >> >>
> > >> >> >> >> >> partitions
> > >> >> >> >> >> major minor #blocks name
> > >> >> >> >> >>
> > >> >> >> >> >> 8 0 5860098048 sda
> > >> >> >> >> >> 8 1 1953126441 sda1
> > >> >> >> >> >> 8 2 1953600390 sda2
> > >> >> >> >> >> 8 16 976762584 sdb
> > >> >> >> >> >> 8 17 96847821 sdb1
> > >> >> >> >> >> 8 18 1 sdb2
> > >> >> >> >> >> 8 21 6040408 sdb5
> > >> >> >> >> >> 8 22 855943137 sdb6
> > >> >> >> >> >>
> > >> >> >> >> >>
> > >> >> >> >> >> The box is a dual core intel
> > >> >> >> >> >>
> > >> >> >> >> >> lspci
> > >> >> >> >> >> 00:00.0 Host bridge: nVidia Corporation C55 Host
> Bridge (rev a2)
> > >> >> >> >> >> 00:00.1 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:00.2 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:00.3 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:00.4 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:00.5 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a2)
> > >> >> >> >> >> 00:00.6 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:00.7 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.0 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.1 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.2 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.3 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.4 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.5 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:01.6 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:02.0 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:02.1 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:02.2 RAM memory: nVidia Corporation C55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:03.0 PCI bridge: nVidia Corporation C55 PCI
> Express bridge (rev a1)
> > >> >> >> >> >> 00:06.0 PCI bridge: nVidia Corporation C55 PCI
> Express bridge (rev a1)
> > >> >> >> >> >> 00:07.0 PCI bridge: nVidia Corporation C55 PCI
> Express bridge (rev a1)
> > >> >> >> >> >> 00:09.0 RAM memory: nVidia Corporation MCP55 Memory
> Controller (rev a1)
> > >> >> >> >> >> 00:0a.0 ISA bridge: nVidia Corporation MCP55 LPC
> Bridge (rev a2)
> > >> >> >> >> >> 00:0a.1 SMBus: nVidia Corporation MCP55 SMBus (rev
> a2)
> > >> >> >> >> >> 00:0b.0 USB Controller: nVidia Corporation MCP55 USB
> Controller (rev a1)
> > >> >> >> >> >> 00:0b.1 USB Controller: nVidia Corporation MCP55 USB
> Controller (rev a2)
> > >> >> >> >> >> 00:0d.0 IDE interface: nVidia Corporation MCP55 IDE
> (rev a1)
> > >> >> >> >> >> 00:0e.0 IDE interface: nVidia Corporation MCP55 SATA
> Controller (rev a2)
> > >> >> >> >> >> 00:0e.1 IDE interface: nVidia Corporation MCP55 SATA
> Controller (rev a2)
> > >> >> >> >> >> 00:0e.2 IDE interface: nVidia Corporation MCP55 SATA
> Controller (rev a2)
> > >> >> >> >> >> 00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI
> bridge (rev a2)
> > >> >> >> >> >> 00:11.0 Bridge: nVidia Corporation MCP55 Ethernet
> (rev a2)
> > >> >> >> >> >> 00:12.0 Bridge: nVidia Corporation MCP55 Ethernet
> (rev a2)
> > >> >> >> >> >> 00:13.0 PCI bridge: nVidia Corporation MCP55 PCI
> Express bridge (rev a2)
> > >> >> >> >> >> 00:14.0 PCI bridge: nVidia Corporation MCP55 PCI
> Express bridge (rev a2)
> > >> >> >> >> >> 00:15.0 PCI bridge: nVidia Corporation MCP55 PCI
> Express bridge (rev a2)
> > >> >> >> >> >> 00:16.0 PCI bridge: nVidia Corporation MCP55 PCI
> Express bridge (rev a2)
> > >> >> >> >> >> 00:17.0 PCI bridge: nVidia Corporation MCP55 PCI
> Express bridge (rev a2)
> > >> >> >> >> >> 00:18.0 PCI bridge: nVidia Corporation MCP55 PCI
> Express bridge (rev a2)
> > >> >> >> >> >> 01:00.0 VGA compatible controller: nVidia Corporation
> G70 [GeForce
> > >> >> >> >> >> 7600 GS] (rev a1)
> > >> >> >> >> >> 02:00.0 Mass storage controller: Silicon Image, Inc.
> Sil 3531
> > >> >> >> >> >> [SATALink/SATARaid] Serial ATA Controller (rev 01)
> > >> >> >> >> >> 04:07.0 FireWire (IEEE 1394): VIA Technologies, Inc.
> IEEE 1394 Host
> > >> >> >> >> >> Controller (rev c0)
> > >> >> >> >> >> 08:00.0 PCI bridge: Creative Labs Unknown device 7006
> > >> >> >> >> >> 09:00.0 Audio device: Creative Labs [SB X-Fi Xtreme
> Audio] CA0110-IBG
> > >> >> >> >> >> 0b:00.0 RAID bus controller: HighPoint Technologies,
> Inc. Unknown
> > >> >> >> >> >> device 3522 (rev 09)
> > >> >> >> >> >>
> > >> >> >> >> >>
> > >> >> >> >> >>
> > >> >> >> >> >> On Thu, Oct 9, 2008 at 11:35 AM, Ming Zhang
> <blackmagic02881@...> wrote:
> > >> >> >> >> >> > pls always cc to iet list.
> > >> >> >> >> >> >
> > >> >> >> >> >> >
> > >> >> >> >> >> > On Thu, 2008-10-09 at 09:23 -0700, Jeremy
> Custenborder wrote:
> > >> >> >> >> >> >> Ming,
> > >> >> >> >> >> >>
> > >> >> >> >> >> >> What data or logs would you want? I would be happy
> to come up with a
> > >> >> >> >> >> >> test case for you guys. When the box locked I had
> two volumes mounted
> > >> >> >> >> >> >> on a window xp machine. One was a partition
> presented using blockio
> > >> >> >> >> >> >> and the other was a file using fileio. The box wen
> unresponsive but
> > >> >> >> >> >> >> would still return a ping. Existing ssh sessions
> would not do anything
> > >> >> >> >> >> >> nor would the console.
> > >> >> >> >> >> >
> > >> >> >> >> >> > check /var/log/message to see if anything from that
> time range.
> > >> >> >> >> >> >
> > >> >> >> >> >> > try to reproduce it with a latest trunk code. keep
> a logged in console.
> > >> >> >> >> >> > so if ssh does not work, you still have a console.
> also when iet looks
> > >> >> >> >> >> > hangs, try to disconnect the ini and see if iet
> recovers.
> > >> >> >> >> >> >
> > >> >> >> >> >> > also need detail sw&hw information.
> > >> >> >> >> >> >
> > >> >> >> >> >> >
> > >> >> >> >> >> >>
> > >> >> >> >> >> >> J
> > >> >> >> >> >> >>
> > >> >> >> >> >> >>
> > >> >> >> >> >> >>
> > >> >> >> >> >> >> On Thu, Oct 9, 2008 at 5:44 AM, Ming Zhang
> <blackmagic02881@...> wrote:
> > >> >> >> >> >> >> > On Wed, 2008-10-08 at 22:44 -0700, Jeremy
> Custenborder wrote:
> > >> >> >> >> >> >> >> Hello All,
> > >> >> >> >> >> >> >>
> > >> >> >> >> >> >> >> I've run into some compile errors trying to
> build 0.4.16 on a ubuntu
> > >> >> >> >> >> >> >> box with kernel 2.6.26.3. Am I missing
> something? Is 0.4.16 the most
> > >> >> >> >> >> >> >> stable version? Is there a more stable
> revision that I could check
> > >> >> >> >> >> >> >> out at? I also have a box running at changeset
> 162 of trunk which did
> > >> >> >> >> >> >> >> compile successfully but that box locked up
> under heavy load last
> > >> >> >> >> >> >> >> night.
> > >> >> >> >> >> >> >
> > >> >> >> >> >> >> > you need to use the trunk code. latest one is
> r174.
> > >> >> >> >> >> >> >
> > >> >> >> >> >> >> > any error log, message,... about the lockup? we
> need to fix this bug if
> > >> >> >> >> >> >> > have...
> > >> >> >> >> >> >> >
> > >> >> >> >> >> >> >
> > >> >> >> >> >> >> >> Thanks for the assistance!
> > >> >> >> >> >> >> >>
> > >> >> >> >> >> >> >>
> > >> >> >> >> >> >> >>
> > >> >> >> >> >> >> >> In file included from
> > >> >> >> >> >> >>
> >> /home/jeremy/source/iscsitarget/0.4.16/kernel/block-io.c:12:
> > >> >> >> >> >> >> >> include/linux/parser.h:32: error: expected â=â,
> â,â, â;â, âasmâ or
> > >> >> >> >> >> >> >> â__attribute__â before âmatch_strlcpyâ
> > >> >> >> >> >> >> >> make[2]: ***
> [/home/jeremy/source/iscsitarget/0.4.16/kernel/block-io.o] Error 1
> > >> >> >> >> >> >> >> make[1]: ***
> [_module_/home/jeremy/source/iscsitarget/0.4.16/kernel] Error 2
> > >> >> >> >> >> >> >> make: *** [kernel] Error 2
> > >> >> >> >> >> >> >>
> > >> >> >> >> >> >> >>
> -------------------------------------------------------------------------
> > >> >> >> >> >> >> >> This SF.Net email is sponsored by the Moblin
> Your Move Developer's challenge
> > >> >> >> >> >> >> >> Build the coolest Linux based applications with
> Moblin SDK & win great prizes
> > >> >> >> >> >> >> >> Grand prize is a trip for two to an Open Source
> event anywhere in the world
> > >> >> >> >> >> >> >>
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > >> >> >> >> >> >> >> _______________________________________________
> > >> >> >> >> >> >> >> Iscsitarget-devel mailing list
> > >> >> >> >> >> >> >> Iscsitarget-devel@...
> > >> >> >> >> >> >> >>
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> > >> >> >> >> >> >> > --
> > >> >> >> >> >> >> > never so busy...
> > >> >> >> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> > >> >> >> >> >> >> >
> > >> >> >> >> >> >> >
> > >> >> >> >> >> > --
> > >> >> >> >> >> > never so busy...
> > >> >> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> > >> >> >> >> >> >
> > >> >> >> >> >> >
> > >> >> >> >> > --
> > >> >> >> >> > never so busy...
> > >> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> > >> >> >> >> >
> > >> >> >> >> >
> > >> >> >> > --
> > >> >> >> > never so busy...
> > >> >> >> > http://www.linkedin.com/in/blackmagic02881
> > >> >> >> >
> > >> >> >> >
> > >> >> > --
> > >> >> > never so busy...
> > >> >> > http://www.linkedin.com/in/blackmagic02881
> > >> >> >
> > >> >> >
> > >> > --
> > >> > never so busy...
> > >> > http://www.linkedin.com/in/blackmagic02881
> > >> >
> > >> >
> > > --
> > > never so busy...
> > > http://www.linkedin.com/in/blackmagic02881
> > >
> > >

--
never so busy...
http://www.linkedin.com/in/blackmagic02881

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@...
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel

From forum: iscsitarget-devel

Re: Compile Errors

2008-10-12T17:14:40Z

Get ready for some weirdness. I decided to update my kernel to 2.6.27, recompiled iscsi-target off trunk, and it is working perfectly again. I cannot repro the issue anymore and everything is working perfectly. Hehe this is totally annoying because I would love to know the exact cause for the problem. The box ran fine for two months on the previous kernel version. Again thanks for your help it was 1000% appreciated.

J

-----Original Message-----
From: Ming Zhang [mailto:blackmagic02881@...]
Sent: Friday, October 10, 2008 6:09 AM
To: Jeremy Custenborder
Cc: iscsitarget-devel@...
Subject: Re: [Iscsitarget-devel] Compile Errors

On Thu, 2008-10-09 at 19:40 -0700, Jeremy Custenborder wrote:

> On Thu, Oct 9, 2008 at 5:49 PM, Ming Zhang <blackmagic02881@...> wrote:
> > On Thu, 2008-10-09 at 17:39 -0700, Jeremy Custenborder wrote:
> >> On Thu, Oct 9, 2008 at 4:52 PM, Ming Zhang <blackmagic02881@...> wrote:
> >> > On Thu, 2008-10-09 at 15:41 -0700, Jeremy Custenborder wrote:
> >> >> no they are on different hardware. A snippit of my config is below.
> >> >> Thanks for the assistance, I really appreciate it. /dev/sda is a 6.1TB
> >> >> disk that is presented by a Highpoint 3522 raid controller.
> >> >> /root/iscsidisk is a file on a single disk attached to the motherboard
> >> >> of the box. This is also the same drive that the OS is installed.
> >> >> /root/iscsidisk is a sparse file on ext3 that is 500gb in size.
> >> >> /dev/sda1 and /dev/sda2 are 2TB partitions presented directly to
> >> >> iscsi-target
> >> >>
> >> >> Target iqn.2008-08.msp.localdomain:volume1
> >> >> Lun 0 Path=/dev/sda1,Type=blockio
> >> >> Target iqn.2008-08.msp.localdomain:volume2
> >> >> Lun 1 Path=/dev/sda2,Type=blockio
> >> >
> >> > so these 2 share same raid. raid5? any nvram cache?
> >>
> >> correct /dev/sda* is on the same raid controller running raid 6 across
> >> 8x1TB drives. The controller has 256MB of cache and each drive has
> >> 32mb of cache. /root/iscsidisk is a sparse file on a regular 1TB sata
> >> disk that also has 32MB of cache.
> >>
> >>
> >> > i guess when lock up, u copy between these 2?
> >> Correct The problem happened when copying from /dev/sda2 to /root/iscsidisk.
> >
> > reading from raid6, will not be a bottleneck. but writing to a sparse
> > file under ext3 on top of one disk might be slow. though should not lead
> > to lock up.
> >
> >>
> >>
> >>
> >> > btw, do you know how to use crash? a linux utility allow u to examine
> >> > kernel lively?
> >>
> >> no I'm a little bit of a nub. Can you point me at a tutorial? I know
> >> windows kernel debugging but have never worked with linux kernel
> >> bugging.
> >
> > then give up, this one is not a easy one, especially under ubuntu.
>
> nah lets give it a shot. I'm a nub to linux but not development. I've
> got a couple
> rockstars at the office that can help me out if I get stuck. I'll look
> into getting myself up to speed.

i know you are good at development (via linkedin). actually you should
be able to figure this out. ;)

>
>
> > btw, ubuntu split the kernel log to different files under /var/log.
> > could you reproduce the bug and run dmesg and see if anything.
> >
> > check meminfo to see if out of memory. enable nmi and see if any dead
> > lock.
>
> I'll give it a try
>
> > when u got that lock up. the machine just hangs and have to cold reset,
> > or eventually it came back.
>
> when it hangs it totally hangs and I have to power cycle the hardware.

try to prepare your system with NMI enabled and with kdump enabled. once
this happen, force a crash dump and we can check which thread stuck.
because of deadlock, or because of OOM.

i am not familiar with ubuntu, otherwise can give your exact
instruction.

>
>
> >>
> >>
> >> >> Target iqn.2008-08.msp.localdomain:sparsedisk
> >> >> Lun 2 Path=/root/iscsidisk,Type=fileio
> >> >>
> >> >>
> >> >> On Thu, Oct 9, 2008 at 2:38 PM, Ming Zhang <blackmagic02881@...> wrote:
> >> >> > On Thu, 2008-10-09 at 14:32 -0700, Jeremy Custenborder wrote:
> >> >> >> yep it's 64 bit. I've watched it under load and all seems pretty well.
> >> >> >> These errors have happened when copying data over night. That might
> >> >> >> make things interesting getting the perfect slice of data. I had this
> >> >> >> configuration working pretty well based off trunk from a while ago.
> >> >> >> Like an idiot I did not back up that source and now I'm on the quest
> >> >> >> for the stable version again. Trunk had locked up on me before that is
> >> >> >> why I tried 162.
> >> >> >
> >> >> >>
> >> >> >> The scenario that hung looked like this. I remember seeing the NIC on
> >> >> >> the XP box hitting 30 - 40 % of 1gbps. I'll try to repro the problem
> >> >> >> when I get home tonight.
> >> >> >>
> >> >> >> iscsi-target box --Move Data (Read / Delete)--> XP Box ini 2.07 --
> >> >> >> Write--> same iscsi-target box.
> >> >> >
> >> >> > do these 2 target share same RAID?
> >> >> >
> >> >> >
> >> >> >>
> >> >> >> On Thu, Oct 9, 2008 at 2:11 PM, Ming Zhang <blackmagic02881@...> wrote:
> >> >> >> > btw, when iet hangs, meminfo at that moment is useful as well.
> >> >> >> >
> >> >> >> > also because we can not ssh into the box, a test case allow u to quickly
> >> >> >> > reproduce it will be helpful as well.
> >> >> >> >
> >> >> >> > i assumed it is a 64bit box, right?
> >> >> >> >
> >> >> >> >
> >> >> >> > On Thu, 2008-10-09 at 13:53 -0700, Jeremy Custenborder wrote:
> >> >> >> >> Oh sorry. 6GB.
> >> >> >> >>
> >> >> >> >> cat /proc/meminfo
> >> >> >> >> MemTotal: 6133692 kB
> >> >> >> >> MemFree: 5331500 kB
> >> >> >> >> Buffers: 65408 kB
> >> >> >> >> Cached: 603384 kB
> >> >> >> >> SwapCached: 0 kB
> >> >> >> >> Active: 140008 kB
> >> >> >> >> Inactive: 566232 kB
> >> >> >> >> SwapTotal: 17928500 kB
> >> >> >> >> SwapFree: 17928500 kB
> >> >> >> >> Dirty: 0 kB
> >> >> >> >> Writeback: 0 kB
> >> >> >> >> AnonPages: 37516 kB
> >> >> >> >> Mapped: 19288 kB
> >> >> >> >> Slab: 49284 kB
> >> >> >> >> SReclaimable: 40160 kB
> >> >> >> >> SUnreclaim: 9124 kB
> >> >> >> >> PageTables: 3888 kB
> >> >> >> >> NFS_Unstable: 0 kB
> >> >> >> >> Bounce: 0 kB
> >> >> >> >> WritebackTmp: 0 kB
> >> >> >> >> CommitLimit: 20995344 kB
> >> >> >> >> Committed_AS: 71480 kB
> >> >> >> >> VmallocTotal: 34359738367 kB
> >> >> >> >> VmallocUsed: 302992 kB
> >> >> >> >> VmallocChunk: 34359434691 kB
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> On Thu, Oct 9, 2008 at 1:47 PM, Ming Zhang <blackmagic02881@...> wrote:
> >> >> >> >> > On Thu, 2008-10-09 at 13:38 -0700, Jeremy Custenborder wrote:
> >> >> >> >> >> Below is my hardware information. I will try to repro my problems with
> >> >> >> >> >> against trunk tonight. Sorry about the CC. I was planning on adding
> >> >> >> >> >> the list after I got more specific instructions. I took a look at
> >> >> >> >> >> var/log/messages but did not really write down the time or see
> >> >> >> >> >> anything out of the ordinary.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > RAM size?
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > not a problem. when this happen, try to use top to see which process
> >> >> >> >> > take most cpu. and see if disconnect ini can let the problem go away.
> >> >> >> >> > otherwise it is a hard lock up.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >> Intel Dual core
> >> >> >> >> >> processor : 0
> >> >> >> >> >> vendor_id : GenuineIntel
> >> >> >> >> >> cpu family : 6
> >> >> >> >> >> model : 23
> >> >> >> >> >> model name : Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
> >> >> >> >> >> stepping : 6
> >> >> >> >> >> cpu MHz : 2533.213
> >> >> >> >> >> cache size : 3072 KB
> >> >> >> >> >> physical id : 0
> >> >> >> >> >> siblings : 2
> >> >> >> >> >> jeremy@server:~$ head /proc/version
> >> >> >> >> >> Linux version 2.6.26.3 (root@server) (gcc version 4.2.3 (Ubuntu
> >> >> >> >> >> 4.2.3-2ubuntu7)) #1 SMP Sat Aug 23 04:32:51 PDT 2008
> >> >> >> >> >> jeremy@server:~$ head /proc/swap
> >> >> >> >> >> head: cannot open `/proc/swap' for reading: No such file or directory
> >> >> >> >> >> jeremy@server:~$ head /proc/swaphead /proc/partitions
> >> >> >> >> >> jeremy@server:~$ head /proc/partitions
> >> >> >> >> >> major minor #blocks name
> >> >> >> >> >>
> >> >> >> >> >> 8 0 5860098048 sda
> >> >> >> >> >> 8 1 1953126441 sda1
> >> >> >> >> >> 8 2 1953600390 sda2
> >> >> >> >> >> 8 16 976762584 sdb
> >> >> >> >> >> 8 17 96847821 sdb1
> >> >> >> >> >> 8 18 1 sdb2
> >> >> >> >> >> 8 21 6040408 sdb5
> >> >> >> >> >> 8 22 855943137 sdb6
> >> >> >> >> >> jeremy@server:~$
> >> >> >> >> >>
> >> >> >> >> >> processor : 0
> >> >> >> >> >> vendor_id : GenuineIntel
> >> >> >> >> >> cpu family : 6
> >> >> >> >> >> model : 23
> >> >> >> >> >> model name : Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
> >> >> >> >> >> stepping : 6
> >> >> >> >> >> cpu MHz : 2533.213
> >> >> >> >> >> cache size : 3072 KB
> >> >> >> >> >> physical id : 0
> >> >> >> >> >> siblings : 2
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> Linux version 2.6.26.3 (root@server) (gcc version 4.2.3 (Ubuntu
> >> >> >> >> >> 4.2.3-2ubuntu7)) #1 SMP Sat Aug 23 04:32:51 PDT 2008
> >> >> >> >> >>
> >> >> >> >> >> partitions
> >> >> >> >> >> major minor #blocks name
> >> >> >> >> >>
> >> >> >> >> >> 8 0 5860098048 sda
> >> >> >> >> >> 8 1 1953126441 sda1
> >> >> >> >> >> 8 2 1953600390 sda2
> >> >> >> >> >> 8 16 976762584 sdb
> >> >> >> >> >> 8 17 96847821 sdb1
> >> >> >> >> >> 8 18 1 sdb2
> >> >> >> >> >> 8 21 6040408 sdb5
> >> >> >> >> >> 8 22 855943137 sdb6
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> The box is a dual core intel
> >> >> >> >> >>
> >> >> >> >> >> lspci
> >> >> >> >> >> 00:00.0 Host bridge: nVidia Corporation C55 Host Bridge (rev a2)
> >> >> >> >> >> 00:00.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:00.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:00.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:00.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:00.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a2)
> >> >> >> >> >> 00:00.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:00.7 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:01.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:02.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:02.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:02.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
> >> >> >> >> >> 00:03.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
> >> >> >> >> >> 00:06.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
> >> >> >> >> >> 00:07.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
> >> >> >> >> >> 00:09.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1)
> >> >> >> >> >> 00:0a.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2)
> >> >> >> >> >> 00:0a.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2)
> >> >> >> >> >> 00:0b.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
> >> >> >> >> >> 00:0b.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)
> >> >> >> >> >> 00:0d.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
> >> >> >> >> >> 00:0e.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
> >> >> >> >> >> 00:0e.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
> >> >> >> >> >> 00:0e.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
> >> >> >> >> >> 00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI bridge (rev a2)
> >> >> >> >> >> 00:11.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
> >> >> >> >> >> 00:12.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
> >> >> >> >> >> 00:13.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
> >> >> >> >> >> 00:14.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
> >> >> >> >> >> 00:15.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
> >> >> >> >> >> 00:16.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
> >> >> >> >> >> 00:17.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
> >> >> >> >> >> 00:18.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
> >> >> >> >> >> 01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce
> >> >> >> >> >> 7600 GS] (rev a1)
> >> >> >> >> >> 02:00.0 Mass storage controller: Silicon Image, Inc. Sil 3531
> >> >> >> >> >> [SATALink/SATARaid] Serial ATA Controller (rev 01)
> >> >> >> >> >> 04:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
> >> >> >> >> >> Controller (rev c0)
> >> >> >> >> >> 08:00.0 PCI bridge: Creative Labs Unknown device 7006
> >> >> >> >> >> 09:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
> >> >> >> >> >> 0b:00.0 RAID bus controller: HighPoint Technologies, Inc. Unknown
> >> >> >> >> >> device 3522 (rev 09)
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> On Thu, Oct 9, 2008 at 11:35 AM, Ming Zhang <blackmagic02881@...> wrote:
> >> >> >> >> >> > pls always cc to iet list.
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > On Thu, 2008-10-09 at 09:23 -0700, Jeremy Custenborder wrote:
> >> >> >> >> >> >> Ming,
> >> >> >> >> >> >>
> >> >> >> >> >> >> What data or logs would you want? I would be happy to come up with a
> >> >> >> >> >> >> test case for you guys. When the box locked I had two volumes mounted
> >> >> >> >> >> >> on a window xp machine. One was a partition presented using blockio
> >> >> >> >> >> >> and the other was a file using fileio. The box wen unresponsive but
> >> >> >> >> >> >> would still return a ping. Existing ssh sessions would not do anything
> >> >> >> >> >> >> nor would the console.
> >> >> >> >> >> >
> >> >> >> >> >> > check /var/log/message to see if anything from that time range.
> >> >> >> >> >> >
> >> >> >> >> >> > try to reproduce it with a latest trunk code. keep a logged in console.
> >> >> >> >> >> > so if ssh does not work, you still have a console. also when iet looks
> >> >> >> >> >> > hangs, try to disconnect the ini and see if iet recovers.
> >> >> >> >> >> >
> >> >> >> >> >> > also need detail sw&hw information.
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> >>
> >> >> >> >> >> >> J
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> On Thu, Oct 9, 2008 at 5:44 AM, Ming Zhang <blackmagic02881@...> wrote:
> >> >> >> >> >> >> > On Wed, 2008-10-08 at 22:44 -0700, Jeremy Custenborder wrote:
> >> >> >> >> >> >> >> Hello All,
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >> I've run into some compile errors trying to build 0.4.16 on a ubuntu
> >> >> >> >> >> >> >> box with kernel 2.6.26.3. Am I missing something? Is 0.4.16 the most
> >> >> >> >> >> >> >> stable version? Is there a more stable revision that I could check
> >> >> >> >> >> >> >> out at? I also have a box running at changeset 162 of trunk which did
> >> >> >> >> >> >> >> compile successfully but that box locked up under heavy load last
> >> >> >> >> >> >> >> night.
> >> >> >> >> >> >> >
> >> >> >> >> >> >> > you need to use the trunk code. latest one is r174.
> >> >> >> >> >> >> >
> >> >> >> >> >> >> > any error log, message,... about the lockup? we need to fix this bug if
> >> >> >> >> >> >> > have...
> >> >> >> >> >> >> >
> >> >> >> >> >> >> >
> >> >> >> >> >> >> >> Thanks for the assistance!
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >> In file included from
> >> >> >> >> >> >> >> /home/jeremy/source/iscsitarget/0.4.16/kernel/block-io.c:12:
> >> >> >> >> >> >> >> include/linux/parser.h:32: error: expected â=â, â,â, â;â, âasmâ or
> >> >> >> >> >> >> >> â__attribute__â before âmatch_strlcpyâ
> >> >> >> >> >> >> >> make[2]: *** [/home/jeremy/source/iscsitarget/0.4.16/kernel/block-io.o] Error 1
> >> >> >> >> >> >> >> make[1]: *** [_module_/home/jeremy/source/iscsitarget/0.4.16/kernel] Error 2
> >> >> >> >> >> >> >> make: *** [kernel] Error 2
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >> -------------------------------------------------------------------------
> >> >> >> >> >> >> >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> >> >> >> >> >> >> >> Build the coolest Linux based applications with Moblin SDK & win great prizes
> >> >> >> >> >> >> >> Grand prize is a trip for two to an Open Source event anywhere in the world
> >> >> >> >> >> >> >> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >> >> >> >> >> >> >> _______________________________________________
> >> >> >> >> >> >> >> Iscsitarget-devel mailing list
> >> >> >> >> >> >> >> Iscsitarget-devel@...
> >> >> >> >> >> >> >> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
> >> >> >> >> >> >> > --
> >> >> >> >> >> >> > never so busy...
> >> >> >> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> >> >> >> >> >> >> >
> >> >> >> >> >> >> >
> >> >> >> >> >> > --
> >> >> >> >> >> > never so busy...
> >> >> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > never so busy...
> >> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> > --
> >> >> >> > never so busy...
> >> >> >> > http://www.linkedin.com/in/blackmagic02881
> >> >> >> >
> >> >> >> >
> >> >> > --
> >> >> > never so busy...
> >> >> > http://www.linkedin.com/in/blackmagic02881
> >> >> >
> >> >> >
> >> > --
> >> > never so busy...
> >> > http://www.linkedin.com/in/blackmagic02881
> >> >
> >> >
> > --
> > never so busy...
> > http://www.linkedin.com/in/blackmagic02881
> >
> >

From forum: iscsitarget-devel