Re: Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Well, you see me glad that this fixes your problems. You might want to see with Jack Vogel who maintains the Intel drivers, if you can track down the issue and perhaps even find a fix for it. Taking the liberty of CCing you Jack. 2012/4/18 Eugen Konkov : > Hi, Damien. > > With this configuration works without reboots > > ifconfig_igb0="-rxcsum -txcsum -lro -tso up" > ifconfig_igb1="-rxcsum -txcsum -lro -tso up" > ifconfig_igb2="-rxcsum -txcsum -lro -tso -vlanhwtag up" > ifconfig_igb3="-rxcsum -txcsum -lro -tso up" > > > igb0 has only one vlan > igb1 has two vlans > igb2 has 16 vlans > igb3 has 4 vlans > > > if igb2 has vlanhwtag enabled then server starts to reboot > > DF> Yes, I suggest you try with "-vlanhwtag" as well. > DF> If that stops your unwanted reboots, you may want to remove it and see > DF> if the situation changes. > > > DF> 2012/4/12 Коньков Евгений : >>> Now i350 is configured as: >>> >>> /etc/rc.conf >>> ## TCP/IP >>> ifconfig_igb0="-rxcsum -txcsum -lro -tso up" >>> ifconfig_igb1="-rxcsum -txcsum -lro -tso up" >>> ifconfig_igb2="-rxcsum -txcsum -lro -tso up" >>> ifconfig_igb3="-rxcsum -txcsum -lro -tso up" >>> >>> # ifconfig -m igb1 >>> igb1: flags=8843 metric 0 mtu 1500 >>> >>> options=400b8 >>> >>> capabilities=505bb >>> ether a0:36:9f:00:66:a5 >>> media: Ethernet autoselect (1000baseT ) >>> status: active >>> supported media: >>> media autoselect >>> media 1000baseT >>> media 1000baseT mediaopt full-duplex >>> media 100baseTX mediaopt full-duplex >>> media 100baseTX >>> media 10baseT/UTP mediaopt full-duplex >>> media 10baseT/UTP >>> >>> #pciconf -lv >>> igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 >>> rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> >>> >>> >>> Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? >>> >>> PS. I will try to disable those after the holidays >>> >>> DF> Try disabling hardware VLAN tagging like so, I know we had problems a >>> DF> few years back with it. >>> >>> DF> in /etc/rc.conf : >>> DF> ifconfig_igb2=" -vlanhwtag -tso -lro up" >>> >>> >>> DF> 2012/4/11 KES : > > > Пересылаемое сообщение > 11.04.2012, 13:14, "KES" : > > 10.04.2012, 08:50, "Da Rock" > : > >> On 04/10/12 05:02, Коньков Евгений wrote: >>> Yes, I have tested. >>> and on this hardware on this OS it works from Fri Feb 24 17:07:48 >>> UTC 2012 >>> but last two days: >>> reboot ~ Mon Apr 9 19:50 >>> reboot ~ Mon Apr 9 18:30 >>> reboot ~ Sun Apr 8 20:55 >>> reboot ~ Sun Apr 8 20:00 >>> reboot ~ Sun Apr 8 19:49 >>> reboot ~ Sun Apr 8 17:43 >>> reboot ~ Sun Apr 8 10:58 >>> reboot ~ Sat Apr 7 21:13 >>> reboot ~ Sat Apr 7 16:37 >>> reboot ~ Sat Apr 7 16:07 >>> >>> I remembered. One thing changed. >>> I add vlans to igb2, but no traffic flow on that devices yet. >> Perhaps you should test removing the vlans and see if things improve? > > I have removed vlans, two day server works without reboots > >>> Before this I have use: igb0, igb1, igb3 >>> igb0@pci0:1:0:0: class=0x02 card=0x00018086 >>> chip=0x15218086 rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> igb1@pci0:1:0:1: class=0x02 card=0x00018086 >>> chip=0x15218086 rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> igb2@pci0:1:0:2: class=0x02 card=0x00018086 >>> chip=0x15218086 rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> igb3@pci0:1:0:3: class=0x02 card=0x00018086 >>> chip=0x15218086 rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> >>> ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 >>> vlandev igb2" #nALL >>> ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 >>> vlandev igb2" #n2 p24 >>> ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 >>> vlandev igb2" #n1 p23 >>> ifconfig_vlan103="inet 192.168.3.1 netmask 255.2
Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Hi, Damien. With this configuration works without reboots ifconfig_igb0="-rxcsum -txcsum -lro -tso up" ifconfig_igb1="-rxcsum -txcsum -lro -tso up" ifconfig_igb2="-rxcsum -txcsum -lro -tso -vlanhwtag up" ifconfig_igb3="-rxcsum -txcsum -lro -tso up" igb0 has only one vlan igb1 has two vlans igb2 has 16 vlans igb3 has 4 vlans if igb2 has vlanhwtag enabled then server starts to reboot DF> Yes, I suggest you try with "-vlanhwtag" as well. DF> If that stops your unwanted reboots, you may want to remove it and see DF> if the situation changes. DF> 2012/4/12 Коньков Евгений : >> Now i350 is configured as: >> >> /etc/rc.conf >> ## TCP/IP >> ifconfig_igb0="-rxcsum -txcsum -lro -tso up" >> ifconfig_igb1="-rxcsum -txcsum -lro -tso up" >> ifconfig_igb2="-rxcsum -txcsum -lro -tso up" >> ifconfig_igb3="-rxcsum -txcsum -lro -tso up" >> >> # ifconfig -m igb1 >> igb1: flags=8843 metric 0 mtu 1500 >> >> options=400b8 >> >> capabilities=505bb >> ether a0:36:9f:00:66:a5 >> media: Ethernet autoselect (1000baseT ) >> status: active >> supported media: >> media autoselect >> media 1000baseT >> media 1000baseT mediaopt full-duplex >> media 100baseTX mediaopt full-duplex >> media 100baseTX >> media 10baseT/UTP mediaopt full-duplex >> media 10baseT/UTP >> >> #pciconf -lv >> igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> >> >> >> Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? >> >> PS. I will try to disable those after the holidays >> >> DF> Try disabling hardware VLAN tagging like so, I know we had problems a >> DF> few years back with it. >> >> DF> in /etc/rc.conf : >> DF> ifconfig_igb2=" -vlanhwtag -tso -lro up" >> >> >> DF> 2012/4/11 KES : Пересылаемое сообщение 11.04.2012, 13:14, "KES" : 10.04.2012, 08:50, "Da Rock" : > On 04/10/12 05:02, Коньков Евгений wrote: >> Yes, I have tested. >> and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC >> 2012 >> but last two days: >> reboot ~ Mon Apr 9 19:50 >> reboot ~ Mon Apr 9 18:30 >> reboot ~ Sun Apr 8 20:55 >> reboot ~ Sun Apr 8 20:00 >> reboot ~ Sun Apr 8 19:49 >> reboot ~ Sun Apr 8 17:43 >> reboot ~ Sun Apr 8 10:58 >> reboot ~ Sat Apr 7 21:13 >> reboot ~ Sat Apr 7 16:37 >> reboot ~ Sat Apr 7 16:07 >> >> I remembered. One thing changed. >> I add vlans to igb2, but no traffic flow on that devices yet. > Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots >> Before this I have use: igb0, igb1, igb3 >> igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> >> ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 >> vlandev igb2" #nALL >> ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 >> vlandev igb2" #n2 p24 >> ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 >> vlandev igb2" #n1 p23 >> ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 >> vlandev igb2" #n3 p22 >> ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 >> vlandev igb2" #n7,9 p21 >> ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 >> vlandev igb2" #n11 p20 >> ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 >> vlandev igb2" #n13 p19 >> ifconfig_vlan107="inet 192.168.7.
Re[4]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Здравствуйте, Damien. Вы писали 13 апреля 2012 г., 4:42:31: DF> Yes, I suggest you try with "-vlanhwtag" as well. DF> If that stops your unwanted reboots, you may want to remove it and see DF> if the situation changes. igb0: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a4 media: Ethernet autoselect (1000baseT ) status: active igb1: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT ) status: active igb2: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a6 media: Ethernet autoselect (1000baseT ) status: active igb3: flags=8843 metric 0 mtu 1500 options=400b8 ether a0:36:9f:00:66:a7 media: Ethernet autoselect (1000baseT ) status: active vlan407: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a4 inet netmask 0xfff8 broadcast media: Ethernet autoselect (1000baseT ) status: active vlan: 407 parent interface: igb0 vlan408: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a5 inet x netmask 0xfff8 broadcast xxx media: Ethernet autoselect (1000baseT ) status: active vlan: 408 parent interface: igb1 vlan492: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a5 inet netmask 0xfff8 broadcast x media: Ethernet autoselect (1000baseT ) status: active vlan: 492 parent interface: igb1 vlan70: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet netmask 0xfe00 broadcast xx media: Ethernet autoselect (1000baseT ) status: active vlan: 70 parent interface: igb3 vlan71: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxx netmask 0xfe00 broadcast xxx media: Ethernet autoselect (1000baseT ) status: active vlan: 71 parent interface: igb3 vlan72: flags=8002 metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: vlan73: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet x netmask 0xfe00 broadcast x media: Ethernet autoselect (1000baseT ) status: active vlan: 73 parent interface: igb3 vlan74: flags=8002 metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: vlan75: flags=8002 metric 0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: vlan76: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a7 inet xxx netmask 0xfe00 broadcast xxx media: Ethernet autoselect (1000baseT ) status: active vlan: 76 parent interface: igb3 vlan100: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan101: flags=8843 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 inet xx netmask 0xff00 broadcast xxx media: Ethernet autoselect (1000baseT ) status: active vlan: 101 parent interface: igb2 vlan102: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan103: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan104: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan105: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan106: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan107: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan108: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan109: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan110: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan111: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan112: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan113: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan114: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan115: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: vlan: 0 parent interface: vlan115: flags=8803 metric 0 mtu 1500 ether a0:36:9f:00:66:a6 vlan: 0 parent interface: With this config no 'REBOOT' happen When just assign vlan100, 102-115 to igb2 and add IPs to those interfaces (no any traffic on those vlans yet) server starts
Re: Re[2]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Yes, I suggest you try with "-vlanhwtag" as well. If that stops your unwanted reboots, you may want to remove it and see if the situation changes. 2012/4/12 Коньков Евгений : > Now i350 is configured as: > > /etc/rc.conf > ## TCP/IP > ifconfig_igb0="-rxcsum -txcsum -lro -tso up" > ifconfig_igb1="-rxcsum -txcsum -lro -tso up" > ifconfig_igb2="-rxcsum -txcsum -lro -tso up" > ifconfig_igb3="-rxcsum -txcsum -lro -tso up" > > # ifconfig -m igb1 > igb1: flags=8843 metric 0 mtu 1500 > options=400b8 > > capabilities=505bb > ether a0:36:9f:00:66:a5 > media: Ethernet autoselect (1000baseT ) > status: active > supported media: > media autoselect > media 1000baseT > media 1000baseT mediaopt full-duplex > media 100baseTX mediaopt full-duplex > media 100baseTX > media 10baseT/UTP mediaopt full-duplex > media 10baseT/UTP > > #pciconf -lv > igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > > > Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? > > PS. I will try to disable those after the holidays > > DF> Try disabling hardware VLAN tagging like so, I know we had problems a > DF> few years back with it. > > DF> in /etc/rc.conf : > DF> ifconfig_igb2=" -vlanhwtag -tso -lro up" > > > DF> 2012/4/11 KES : >>> >>> >>> Пересылаемое сообщение >>> 11.04.2012, 13:14, "KES" : >>> >>> 10.04.2012, 08:50, "Da Rock" : >>> On 04/10/12 05:02, Коньков Евгений wrote: > Yes, I have tested. > and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC > 2012 > but last two days: > reboot ~ Mon Apr 9 19:50 > reboot ~ Mon Apr 9 18:30 > reboot ~ Sun Apr 8 20:55 > reboot ~ Sun Apr 8 20:00 > reboot ~ Sun Apr 8 19:49 > reboot ~ Sun Apr 8 17:43 > reboot ~ Sun Apr 8 10:58 > reboot ~ Sat Apr 7 21:13 > reboot ~ Sat Apr 7 16:37 > reboot ~ Sat Apr 7 16:07 > > I remembered. One thing changed. > I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? >>> >>> I have removed vlans, two day server works without reboots >>> > Before this I have use: igb0, igb1, igb3 > igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 > vlandev igb2" #nALL > ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 > vlandev igb2" #n2 p24 > ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 > vlandev igb2" #n1 p23 > ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 > vlandev igb2" #n3 p22 > ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 > vlandev igb2" #n7,9 p21 > ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 > vlandev igb2" #n11 p20 > ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 > vlandev igb2" #n13 p19 > ifconfig_vlan107="inet 192.168.7.1 netmask 255.255.255.0 vlan 107 > vlandev igb2" #n223 p18 > ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108 > vlandev igb2" #n225 p17 > ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109 > vlandev igb2" #n221 p16 > ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 > vlandev igb2" #n229 p15 > ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 > vlandev igb2" #n233 p14 > ifconfig_vlan112="inet 192.16
Re[2]: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Now i350 is configured as: /etc/rc.conf ## TCP/IP ifconfig_igb0="-rxcsum -txcsum -lro -tso up" ifconfig_igb1="-rxcsum -txcsum -lro -tso up" ifconfig_igb2="-rxcsum -txcsum -lro -tso up" ifconfig_igb3="-rxcsum -txcsum -lro -tso up" # ifconfig -m igb1 igb1: flags=8843 metric 0 mtu 1500 options=400b8 capabilities=505bb ether a0:36:9f:00:66:a5 media: Ethernet autoselect (1000baseT ) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP #pciconf -lv igb0@pci0:1:0:0:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet Do I need to disable VLAN_HWCSUM, VLAN_HWFILTER,VLAN_HWTSO also? PS. I will try to disable those after the holidays DF> Try disabling hardware VLAN tagging like so, I know we had problems a DF> few years back with it. DF> in /etc/rc.conf : DF> ifconfig_igb2=" -vlanhwtag -tso -lro up" DF> 2012/4/11 KES : >> >> >> Пересылаемое сообщение >> 11.04.2012, 13:14, "KES" : >> >> 10.04.2012, 08:50, "Da Rock" : >> >>> On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. >>> Perhaps you should test removing the vlans and see if things improve? >> >> I have removed vlans, two day server works without reboots >> Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2" #nALL ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2" #n2 p24 ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2" #n1 p23 ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2" #n3 p22 ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2" #n7,9 p21 ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2" #n11 p20 ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2" #n13 p19 ifconfig_vlan107="inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2" #n223 p18 ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2" #n225 p17 ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2" #n221 p16 ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2" #n229 p15 ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2" #n233 p14 ifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2" #n231 p13 ifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2" #n237 p12 ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2" #n424 p11 ifconfig_vlan115="inet 192.168.15.1 n
Re: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Try disabling hardware VLAN tagging like so, I know we had problems a few years back with it. in /etc/rc.conf : ifconfig_igb2=" -vlanhwtag -tso -lro up" 2012/4/11 KES : > > > Пересылаемое сообщение > 11.04.2012, 13:14, "KES" : > > 10.04.2012, 08:50, "Da Rock" : > >> On 04/10/12 05:02, Коньков Евгений wrote: >>> Yes, I have tested. >>> and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC >>> 2012 >>> but last two days: >>> reboot ~ Mon Apr 9 19:50 >>> reboot ~ Mon Apr 9 18:30 >>> reboot ~ Sun Apr 8 20:55 >>> reboot ~ Sun Apr 8 20:00 >>> reboot ~ Sun Apr 8 19:49 >>> reboot ~ Sun Apr 8 17:43 >>> reboot ~ Sun Apr 8 10:58 >>> reboot ~ Sat Apr 7 21:13 >>> reboot ~ Sat Apr 7 16:37 >>> reboot ~ Sat Apr 7 16:07 >>> >>> I remembered. One thing changed. >>> I add vlans to igb2, but no traffic flow on that devices yet. >> Perhaps you should test removing the vlans and see if things improve? > > I have removed vlans, two day server works without reboots > >>> Before this I have use: igb0, igb1, igb3 >>> igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 >>> rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 >>> rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 >>> rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 >>> rev=0x01 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> subclass = ethernet >>> >>> ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 >>> vlandev igb2" #nALL >>> ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 >>> vlandev igb2" #n2 p24 >>> ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 >>> vlandev igb2" #n1 p23 >>> ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 >>> vlandev igb2" #n3 p22 >>> ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 >>> vlandev igb2" #n7,9 p21 >>> ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 >>> vlandev igb2" #n11 p20 >>> ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 >>> vlandev igb2" #n13 p19 >>> ifconfig_vlan107="inet 192.168.7.1 netmask 255.255.255.0 vlan 107 >>> vlandev igb2" #n223 p18 >>> ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108 >>> vlandev igb2" #n225 p17 >>> ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109 >>> vlandev igb2" #n221 p16 >>> ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 >>> vlandev igb2" #n229 p15 >>> ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 >>> vlandev igb2" #n233 p14 >>> ifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 >>> vlandev igb2" #n231 p13 >>> ifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 >>> vlandev igb2" #n237 p12 >>> ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 >>> vlandev igb2" #n424 p11 >>> ifconfig_vlan115="inet 192.168.15.1 netmask 255.255.255.0 vlan 115 >>> vlandev igb2" # >>> >>> PAP> Nothing logged in /var/log/* or crashes that exist in /var/crash >>> PAP> would indicate to me some sort of hardware related problem. >>> PAP> Have you tested your hardware lately and know that it is in >>> operational order? >>> >>> PAP> ~Paul >>> >>> PAP> On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: > Hi. > > Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN > FAST FSCK > Apr 9 19:51:58 fsck: > Apr 9 19:51:58 fsck: > Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck > MANUALLY. > Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG > Apr 9 20:09:22 kernel: > > running manually: > # fsck -y /dev/ad8s1e > ** /dev/ad8s1e (NO WRITE) > ** Last Mounted on /tmp > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 99 files, 10 used, 506477 free (45 frags, 63304 blocks,
Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Пересылаемое сообщение 11.04.2012, 13:14, "KES" : 10.04.2012, 08:50, "Da Rock" : > On 04/10/12 05:02, Коньков Евгений wrote: >> Yes, I have tested. >> and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 >> but last two days: >> reboot ~ Mon Apr 9 19:50 >> reboot ~ Mon Apr 9 18:30 >> reboot ~ Sun Apr 8 20:55 >> reboot ~ Sun Apr 8 20:00 >> reboot ~ Sun Apr 8 19:49 >> reboot ~ Sun Apr 8 17:43 >> reboot ~ Sun Apr 8 10:58 >> reboot ~ Sat Apr 7 21:13 >> reboot ~ Sat Apr 7 16:37 >> reboot ~ Sat Apr 7 16:07 >> >> I remembered. One thing changed. >> I add vlans to igb2, but no traffic flow on that devices yet. > Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots >> Before this I have use: igb0, igb1, igb3 >> igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> class = network >> subclass = ethernet >> >> ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev >> igb2" #nALL >> ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev >> igb2" #n2 p24 >> ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev >> igb2" #n1 p23 >> ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev >> igb2" #n3 p22 >> ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev >> igb2" #n7,9 p21 >> ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev >> igb2" #n11 p20 >> ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev >> igb2" #n13 p19 >> ifconfig_vlan107="inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev >> igb2" #n223 p18 >> ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev >> igb2" #n225 p17 >> ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev >> igb2" #n221 p16 >> ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev >> igb2" #n229 p15 >> ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev >> igb2" #n233 p14 >> ifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev >> igb2" #n231 p13 >> ifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev >> igb2" #n237 p12 >> ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev >> igb2" #n424 p11 >> ifconfig_vlan115="inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev >> igb2" # >> >> PAP> Nothing logged in /var/log/* or crashes that exist in /var/crash >> PAP> would indicate to me some sort of hardware related problem. >> PAP> Have you tested your hardware lately and know that it is in >> operational order? >> >> PAP> ~Paul >> >> PAP> On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) Server reboot two or three time per day # uname -a FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 before this it works about
Re: fsck problem FreeBSD 8.3
12.04.2012 00:05, Коньков Евгений пишет: > Здравствуйте, Eugene. > > Вы писали 10 апреля 2012 г., 0:39:52: > > EG> 10.04.2012 01:36, Коньков Евгений пишет: >>> Hi. >>> >>> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN >>> FAST FSCK >>> Apr 9 19:51:58 fsck: >>> Apr 9 19:51:58 fsck: >>> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck >>> MANUALLY. >>> Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG >>> Apr 9 20:09:22 kernel: >>> >>> running manually: >>> # fsck -y /dev/ad8s1e >>> ** /dev/ad8s1e (NO WRITE) > > EG> You cannot run fsck on mounted filesystem, unmount it first. > Why not? fsck can do its job at background, on mounted FS. It is run in special mode then, you run fsck not that way. > So I also can run it on mounted FS. "NO WRITE" signals you that it will not be able to fix any problem it encounters. > in this case (as I have showed) it do not find any errors. And if it finds any error on mounted live file system, that would not mean the error really exists. Do NOT run fsck on mounted file system, period. > In any case I have run fsck on this FS when it was dismounted. > There is no any errors. So, you need not bother, your file system has been already fixed. > I think here is only one problem. problem to 'RUN FAST FSCK' No need to, already. Eugene Grosbein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re[2]: fsck problem FreeBSD 8.3
Здравствуйте, Eugene. Вы писали 10 апреля 2012 г., 0:39:52: EG> 10.04.2012 01:36, Коньков Евгений пишет: >> Hi. >> >> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST >> FSCK >> Apr 9 19:51:58 fsck: >> Apr 9 19:51:58 fsck: >> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck >> MANUALLY. >> Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG >> Apr 9 20:09:22 kernel: >> >> running manually: >> # fsck -y /dev/ad8s1e >> ** /dev/ad8s1e (NO WRITE) EG> You cannot run fsck on mounted filesystem, unmount it first. Why not? fsck can do its job at background, on mounted FS. So I also can run it on mounted FS. in this case (as I have showed) it do not find any errors. In any case I have run fsck on this FS when it was dismounted. There is no any errors. I think here is only one problem. problem to 'RUN FAST FSCK' -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck problem FreeBSD 8.3
On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2" #nALL ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2" #n2 p24 ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2" #n1 p23 ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2" #n3 p22 ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2" #n7,9 p21 ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2" #n11 p20 ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2" #n13 p19 ifconfig_vlan107="inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2" #n223 p18 ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2" #n225 p17 ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2" #n221 p16 ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2" #n229 p15 ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2" #n233 p14 ifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2" #n231 p13 ifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2" #n237 p12 ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2" #n424 p11 ifconfig_vlan115="inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev igb2" # PAP> Nothing logged in /var/log/* or crashes that exist in /var/crash PAP> would indicate to me some sort of hardware related problem. PAP> Have you tested your hardware lately and know that it is in operational order? PAP> ~Paul PAP> On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) Server reboot two or three time per day # uname -a FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 before this it works about month without problems /var/crash - empty, in /var/log/messages there is no any messages before crash. Can any help to fix problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck problem FreeBSD 8.3
10.04.2012 01:36, Коньков Евгений пишет: > Hi. > > Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST > FSCK > Apr 9 19:51:58 fsck: > Apr 9 19:51:58 fsck: > Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck > MANUALLY. > Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG > Apr 9 20:09:22 kernel: > > running manually: > # fsck -y /dev/ad8s1e > ** /dev/ad8s1e (NO WRITE) You cannot run fsck on mounted filesystem, unmount it first. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re[2]: fsck problem FreeBSD 8.3
Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3:class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2" #nALL ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2" #n2 p24 ifconfig_vlan102="inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2" #n1 p23 ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2" #n3 p22 ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2" #n7,9 p21 ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2" #n11 p20 ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2" #n13 p19 ifconfig_vlan107="inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2" #n223 p18 ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2" #n225 p17 ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2" #n221 p16 ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2" #n229 p15 ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2" #n233 p14 ifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2" #n231 p13 ifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2" #n237 p12 ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2" #n424 p11 ifconfig_vlan115="inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev igb2" # PAP> Nothing logged in /var/log/* or crashes that exist in /var/crash PAP> would indicate to me some sort of hardware related problem. PAP> Have you tested your hardware lately and know that it is in operational order? PAP> ~Paul PAP> On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: >> Hi. >> >> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST >> FSCK >> Apr 9 19:51:58 fsck: >> Apr 9 19:51:58 fsck: >> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck >> MANUALLY. >> Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG >> Apr 9 20:09:22 kernel: >> >> running manually: >> # fsck -y /dev/ad8s1e >> ** /dev/ad8s1e (NO WRITE) >> ** Last Mounted on /tmp >> ** Phase 1 - Check Blocks and Sizes >> ** Phase 2 - Check Pathnames >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> ** Phase 5 - Check Cyl groups >> 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) >> >> >> Server reboot two or three time per day >> # uname -a >> FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 >> 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 >> >> before this it works about month without problems >> >> /var/crash - empty, in /var/log/messages there is no any messages before >> crash. >> Can any help to fix problem? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck problem FreeBSD 8.3
Nothing logged in /var/log/* or crashes that exist in /var/crash would indicate to me some sort of hardware related problem. Have you tested your hardware lately and know that it is in operational order? ~Paul On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: > Hi. > > Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST > FSCK > Apr 9 19:51:58 fsck: > Apr 9 19:51:58 fsck: > Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck > MANUALLY. > Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG > Apr 9 20:09:22 kernel: > > running manually: > # fsck -y /dev/ad8s1e > ** /dev/ad8s1e (NO WRITE) > ** Last Mounted on /tmp > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) > > > Server reboot two or three time per day > # uname -a > FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 > 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 > > before this it works about month without problems > > /var/crash - empty, in /var/log/messages there is no any messages before > crash. > Can any help to fix problem? > > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/legal/email_disclaimer/ for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
fsck problem FreeBSD 8.3
Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) Server reboot two or three time per day # uname -a FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 before this it works about month without problems /var/crash - empty, in /var/log/messages there is no any messages before crash. Can any help to fix problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: harddisk problem and/or fsck problem?
On Fri, Mar 26, 2004 at 02:09:35PM -0800, Kent Stewart wrote: > > The sequence that is designed to keep your out of trouble is buildworld, > buildkernel, installkernel, boot -s, and installworld, followed by a > mergemaster. > > There are times as the statfs change to current that would render your > system useless until you repair if if you do the installworld before > booting to the new kernel. The sequence is /usr/src/UPDATING is there > for a reason. You can change the order but if it breaks your system, > you could have to repair it using the fixit disk or re-install. > > Kent > Yes, I'm hip to all that... Thanks, again! -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: harddisk problem and/or fsck problem?
On Friday 26 March 2004 01:02 pm, Richard Dawes wrote: > On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote: > > On Friday 26 March 2004 10:06 am, Richard Dawes wrote: > > > Greetings, fellow FreeBSD users! > > > > > > Everything so far works fine for me, until I drop into single- > > > user mode to prep for making world. Even then, it seems OK, > > > except for this alarming output of "fsck -p": > > > > Well, you missed reading something because you are supposed to boot > > -s into single user mode. Then, you don't have write access and the > > fsck works. > > > > BTW, the whole point of booting into single user mode is to avoid a > > bad kernel. When you drop into single user mode, you aren't testing > > the new kernel. > > > > Kent > > Doh! Yes, I guess I was reading too quickly. And of course > it makes sense that I'd not need to fsck and mount things if > I just "drop" into single-user mode. > > But I wasn't yet testing a new kernel... I haven't yet made the > buildworld target. I see later on, though, where I'm supposed > to boot -s after installing a newly built kernel. > The sequence that is designed to keep your out of trouble is buildworld, buildkernel, installkernel, boot -s, and installworld, followed by a mergemaster. There are times as the statfs change to current that would render your system useless until you repair if if you do the installworld before booting to the new kernel. The sequence is /usr/src/UPDATING is there for a reason. You can change the order but if it breaks your system, you could have to repair it using the fixit disk or re-install. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: harddisk problem and/or fsck problem?
On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote: > On Friday 26 March 2004 10:06 am, Richard Dawes wrote: > > Greetings, fellow FreeBSD users! > > > > Everything so far works fine for me, until I drop into single- > > user mode to prep for making world. Even then, it seems OK, > > except for this alarming output of "fsck -p": > > Well, you missed reading something because you are supposed to boot -s > into single user mode. Then, you don't have write access and the fsck > works. > > BTW, the whole point of booting into single user mode is to avoid a bad > kernel. When you drop into single user mode, you aren't testing the new > kernel. > > Kent Doh! Yes, I guess I was reading too quickly. And of course it makes sense that I'd not need to fsck and mount things if I just "drop" into single-user mode. But I wasn't yet testing a new kernel... I haven't yet made the buildworld target. I see later on, though, where I'm supposed to boot -s after installing a newly built kernel. Thanks for your help! -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: harddisk problem and/or fsck problem?
On Friday 26 March 2004 10:06 am, Richard Dawes wrote: > Greetings, fellow FreeBSD users! > > Everything so far works fine for me, until I drop into single- > user mode to prep for making world. Even then, it seems OK, > except for this alarming output of "fsck -p": Well, you missed reading something because you are supposed to boot -s into single user mode. Then, you don't have write access and the fsck works. BTW, the whole point of booting into single user mode is to avoid a bad kernel. When you drop into single user mode, you aren't testing the new kernel. Kent > > /dev/da0s1a: NO WRITE ACCESS > /dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > I run "fsck /dev/da0s1a", and I'm just told of NO WRITE for the > fs, and the phases shown without error. But I *can* write > there -- my / partition. > > OK, FYI -- This happens on 4.9-RELEASE and 5.2.1-RELEASE-i386 > both. I have an IBM UltraStar Ultra160 SCSI disk, model no. > IC35L018UDW210-0 ... Runs on a Tyan S2462 "Thunder K7" dual > Athlon-MP board, using the GENERIC kernel. > > I've run the onboard Adaptec-controller's format and verify > utilities, which I presume run without error, since they just > do their thing without error messages and just say when they're > done. > > I install the above via the "miniinst" CDs, cvsup the lastest > sources, and that's it for usage. But the machine boots and > runs fine otherwise. > > Is this something to really worry about? Is it safe to proceed > with making world? Should I try forcing fsck to do anything? > Or, should I try running fsck having booted from CD? Other > ideas or suggestions? > > Thanks all for any help offered! Cheers, > > -Rich -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
harddisk problem and/or fsck problem?
Greetings, fellow FreeBSD users! Everything so far works fine for me, until I drop into single- user mode to prep for making world. Even then, it seems OK, except for this alarming output of "fsck -p": /dev/da0s1a: NO WRITE ACCESS /dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I run "fsck /dev/da0s1a", and I'm just told of NO WRITE for the fs, and the phases shown without error. But I *can* write there -- my / partition. OK, FYI -- This happens on 4.9-RELEASE and 5.2.1-RELEASE-i386 both. I have an IBM UltraStar Ultra160 SCSI disk, model no. IC35L018UDW210-0 ... Runs on a Tyan S2462 "Thunder K7" dual Athlon-MP board, using the GENERIC kernel. I've run the onboard Adaptec-controller's format and verify utilities, which I presume run without error, since they just do their thing without error messages and just say when they're done. I install the above via the "miniinst" CDs, cvsup the lastest sources, and that's it for usage. But the machine boots and runs fine otherwise. Is this something to really worry about? Is it safe to proceed with making world? Should I try forcing fsck to do anything? Or, should I try running fsck having booted from CD? Other ideas or suggestions? Thanks all for any help offered! Cheers, -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd boot and fsck problem
Dear FreeBSD people I started to learn and used FreeBSD from last year. And I found FreeBSD is really very powerful and lovely. But I am also a little scared of it, for then it has problem, I just do not know how to fix it. Here I came up a big emergent problem this morning, and I wish you can give me your precious advice and help. I have been using a script drivecopy.sh for a couple of months to do full backup once a week. This drivecopy.sh is a small scripts to copy whole IDE HDD (of freeBSD) to another HDD. Please have a look at the attached script drivecopy.sh It worked very fine till yesterday. Last night, As usual,I started ./drivecopy.sh to backup my FreeBSD4.3 server (Disk1) on another HDD(Disk2). Disk2 has been used successfully as backup for more than 10 times with same procedure of ./drivecopy.sh. So it seemed the start up going smoothly, then I left the server room. This morning, when I came to check the server and backup. (which was supposed to have finished). And I surprised to find all those horrible error messages on the console screen: ***start to quote error message ad0s2e: had error reading fsbn 97103692 of 3473456-3473467(ad0s2 bn 97103692; cn 6044 fn 108 sn 28) status=59 error=40 cannot read: BLK 3473456 UNEXPECTED SOFT UPDATE INCONSISTENCY. **end of error message quote So I had to force to suspend the backup process by pressing Ctrl+Z. Then I tried to reboot Disk1. I had problem during the booting process. **start to quote error message chflags: not found chown: not found cd: can't cd to /var/run cd: can't cd to /var/spool/lock /etc/rc: cann't create /var/run/dmesg.boot directory nonexistent cd: can't cd to /var/run /etc/rc: cannot ceate /var/run/clean_var:dirctory nonexitent. Enter full path of shell or return for /bin/sh . **end of error message quote Then I just press Enter and came to the single boot mode. I typed the following command to try to munually fsck the problem partition. #fsck /dev/ad0s2e The console then showed the following message. **/dev/ad0s2e **Last mounted on /www **Phase 1 -check block & size cannot read: BLK 19596336 UNEXPECTED SOFT UPDATE INCONSISTENCY continue [y/n] ... Looks like the manual fsck doesn't working here. Then I tried my luck to boot Disk2.Unfortunately, it showed the same errors as Disk2 during booting. Your advice will be highly appreciated. Jennifer P.S. The attached is my drivecopy.sh,which had worked fine for the previous backup processes except yesterday. So I do not think anything wrong with the drivecopy.sh itself. There must be something wrong with my yesterday's backup process, though I can not find out what it is. drivecopy.sh Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fsck problem
On Mon, 24 Feb 2003 [EMAIL PROTECTED] wrote:
> As I type, the server is in single user mode. The fsck commands
> result in:
> CAN NOT READ: BLK 16
>
Try starting vinum.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
fsck problem
I have a RAID-5 array on /home via vinum. This morning, the server (running 4.8-PRERELEASE, compiled last week) wouldn't allow anyone to login via ssh, imap, or console. So I had someone reboot the server via control-alt-delete. Then it said that not all processes would dia, use ps axl. Of course, since we couldn't login, this was pointless advise. :) We then used the reset button on the chassis. As I type, the server is in single user mode. The fsck commands result in: CAN NOT READ: BLK 16 I've looked at http://docs.freebsd.org/44doc/smm/03.fsck/paper.html and found its information less than encouraging. Since its said to "seek a guru", I was hoping that someone here could help my poor little school district. If this wasn't on vinum, I would assume that my next step would be to assume a dead drive and remove it and move on. However, this is a vinum array. I'm not sure how it could be a bad drive if the array is composed of 4 drives. Any help, pointers, etc. would be GREATLY appreciated. My entire school district is effectively dead in the water until this server is running again. TIA, Jaime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
