Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Apr 2012 08:09:26 +1000
From:      Da Rock <freebsd-questions@herveybayaustralia.com.au>
To:        freebsd-questions@freebsd.org
Subject:   Re: fsck problem FreeBSD 8.3
Message-ID:  <4F835E16.3060502@herveybayaustralia.com.au>
In-Reply-To: <544633848.20120409220236@yandex.ru>
References:  <61227818.20120409213654@yandex.ru> <20120409184308.GX49374@nat.myhome> <544633848.20120409220236@yandex.ru>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00
>      vendor     = 'Intel Corporation'
>      class      = network
>      subclass   = ethernet
> igb1@pci0:1:0:1:        class=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00
>      vendor     = 'Intel Corporation'
>      class      = network
>      subclass   = ethernet
> igb2@pci0:1:0:2:        class=0x020000 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00
>      vendor     = 'Intel Corporation'
>      class      = network
>      subclass   = ethernet
> igb3@pci0:1:0:3:        class=0x020000 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?
>
>




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4F835E16.3060502>