Re: 9-STABLE showing disk timeouts
On Di, 2015-10-20 at 08:21 +0800, Erich Dollansky wrote: > Hi, Hi Erich and list members, > On Mon, 19 Oct 2015 18:05:15 +0200 > Marc Santhoff wrote: > > > What is happening there and why? > > I have the same problem with one specific connection. Can you check the > cable? Can you switch to another connector? I'm relatively sure the cable is OK. I'm aware of SATA cable problems, the "standard" specifies only 50 plugging cycles (or was it 15?). When in charge new cables are used. When the computer is not brand new, the sockets are cleaned at first. BUT, when running the older FreeBSD 9 using the old disc driver anything works. I know, because an xterm with "tail -f /var/log/messages" is running very often and I'd have seen this error before - which I haven't. > > Do I need to worry? > > Not, if it was the connection. Hmmm... For reference: marc@puma:/home/marc > dmesg|grep ata atapci0: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem 0xfe8fa000-0xfe8fbfff irq 18 at device 0.0 on pci3 atapci1: at channel -1 on atapci0 atapci1: AHCI v1.00 controller with 2 3Gbps ports, PM supported ata2: on atapci1 ata3: on atapci1 ata4: at channel 0 on atapci0 atapci2: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe4ffc00-0xfe4f irq 19 at device 17.0 on pci0 atapci2: AHCI v1.20 controller with 4 6Gbps ports, PM supported ata5: at channel 0 on atapci2 ata6: at channel 1 on atapci2 ata7: at channel 2 on atapci2 ata8: at channel 3 on atapci2 atapci3: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: at channel 0 on atapci3 ata1: at channel 1 on atapci3 acd0: DVDR at ata0-slave UDMA100 SATA ad10: 114473MB at ata5-master UDMA100 SATA 3Gb/s ad12: 1907729MB at ata6-master UDMA100 SATA 6Gb/s ad16: 228936MB at ata8-master UDMA100 SATA 6Gb/s cd0 at ata0 bus 0 scbus0 target 1 lun 0 marc@puma:/home/marc > grep timeout /var/log/messages marc@puma:/home/marc > zgrep timeout /var/log/messages* marc@puma:/home/marc > marc@puma:/home/marc > uname -mrs FreeBSD 9.1-STABLE amd64 -- Marc Santhoff ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Reloading iscsi target, iscsi initiator panics
On 1018T2321, Frank de Bot (lists) wrote:
> Frank de Bot wrote:
> > Edward Tomasz Napierała wrote:
> >> On 1015T2005, Frank de Bot (lists) wrote:
> >>> Edward Tomasz Napierała wrote:
> On 1014T2316, Frank de Bot (lists) wrote:
> > Hello,
> >
> > I have a FreeBSD 10.2 server running as iSCSI target. Another FreeBSD
> > 10.2 is an initiator and has several targets used.
> >
> > When I add a target and reload its config with 'service ctld reload',
> > the FreeBSD initiator server panics. It's reproducable (I have a
> > coredump, but I think it's clear what the problem is)
>
> How easy it is to reproduce, eg. does it happen about every time?
> Could you paste the backtrace?
> >>>
> >>> The first time I didn't understand what happened, the second time I
> >>> could relate it directly to the reloading of ctld on the iSCSI, within
> >>> moments the server paniced.
> >>>
> >>> I got 2 backtraces:
> >>>
> >>> First one:
> >>>
> >>> Fatal trap 12: page fault while in kernel mode
> >>> cpuid = 1; softdep_deallocate_dependencies: got error 6 while accessing
> >>
> >> This is the FFS on the initiator side panicing because the device it's
> >> on went away. The softupdates code can't handle that very well.
> >>
> >> I have no idea why the devices went away and then reappeared, as visible
> >> in the logs. What has the changed in the ctl.conf? Do you have any
> >> iscsi-related sysctls set on the initiator side?
> >>
> >
> > I've added a new target in the ctl.conf . On the linux server I also see
> > a brief disconnect, but a reconnect is handled well.
> >
> > I haven't set any sysctl's related to iscsi
> >
> > My ctl.conf is (again anonymized):
> >
> > auth-group my-auth {
> > chap "myiscsi" "verysecret"
> > }
> > portal-group pg0 {
> > discovery-auth-group my-auth
> > listen 10.13.37.2
> > }
> >
> > target iqn.2015-03.lan.my.nas:vmstorage-29 {
> > auth-group my-auth
> > portal-group pg0
> > lun 0 {
> > path /tank/images/iscsi/vmstorage-29/vmstorage-29.img
> > size 20484M
> > blocksize 4096
> > option unmap on
> > }
> > }
> >
> > target iqn.2015-03.lan.my.nas:vmstorage-44 {
> > auth-group my-auth
> > portal-group pg0
> > lun 0 {
> > path /tank/images/iscsi/vmstorage-44/vmstorage-44.img
> > size 102404M
> > blocksize 4096
> > option unmap on
> > }
> > }
> >
> > target iqn.2015-03.lan.my.nas:keyserver.my.nl {
> > auth-group my-auth
> > portal-group pg0
> > lun 0 {
> > path /dev/zvol/tank/hosting_images/keyserver.my.nl
> > blocksize 4096
> > option unmap on
> > }
> > }
> >
> > the vmstorage-44 is last added to the config
> >
>
> I've started up my test environment, but I could not reproduce is there.
> When reloading the target, a
> SCSI sense: UNIT ATTENTION asc:3f,e (Reported LUNs data has changed) is
> reported, but no device is destroyed. All servers are running the same
> kernel and userland 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r28
>
> What can those device disconnects cause?
Well, that's the thing: ctld was written to make really, really sure
that reloading configuration does not affect LUNs and targets which
hadn't changed. So, to be honest - no idea. Are you sure you didn't
restart (as in, stop and then start again) ctld instead of reloading
its configuration?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ntpd and router with a *lot* of addresses
Dear colleagues, Yesterday we'd found/stepped on a bit of trouble: on some of our FreeBSD-based routers (hundreds of vlans, etc): Oct 20 22:12:46 gwn4 ntpd[86421]: ntpd 4.2.4p5-a (1) Oct 20 22:12:46 gwn4 ntpd[86422]: Too many sockets in use, FD_SETSIZE 1024 exceeded Actually, machine has to listen on 123 on just 2-3 interfaces (two upstream vlans and lo0), but googling leads me just to -L option which is not described in the manual page nor seams to work (I did not look at the sources yet though). Is there any way to restrict interfaces on which ntpd is listening (modulo jail, which has another/orthogonal set of restrictions)? As usual -- thanks in advance! :) -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd and router with a *lot* of addresses
On Wed, 2015-10-21 at 01:47 +0300, Dmitry Morozovsky wrote: > Dear colleagues, > > Yesterday we'd found/stepped on a bit of trouble: on some of our > FreeBSD-based > routers (hundreds of vlans, etc): > > Oct 20 22:12:46 gwn4 ntpd[86421]: ntpd 4.2.4p5-a (1) > Oct 20 22:12:46 gwn4 ntpd[86422]: Too many sockets in use, > FD_SETSIZE 1024 exceeded > > Actually, machine has to listen on 123 on just 2-3 interfaces (two > upstream > vlans and lo0), but googling leads me just to -L option which is not > described > in the manual page nor seams to work (I did not look at the sources > yet > though). > > Is there any way to restrict interfaces on which ntpd is listening > (modulo > jail, which has another/orthogonal set of restrictions)? > > As usual -- thanks in advance! :) > > The -L option is in the manpage. Looking at the code, the way ntp 4.2.4p5 decides whether an interface is virtual is by looking for a colon in the name (a comment in the 4.2.8 source uses "eth0:1" as an example). An option that is not in the manpage but should work with 4.2.4p5 is to allow it to listen on only one interface with -I, such as "-I re0". But that doesn't help your needs much because it appears you can only list one interface in 4.2.4p5. If you update to ntp 4.2.8 (the version in ports and standard now in freebsd 10.2 and later) you can use the -I option multiple times to make it listen on some exact set of interfaces. -- Ian ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
