Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Jan 2014 17:55:21 +0100 (CET)
From:      krichy@tvnetwork.hu
To:        Philipp <mailinglists@cypresscreek.de>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: Filesystem errors with VirtIO
Message-ID:  <alpine.DEB.2.10.1401201753220.26535@krichy.tvnetwork.hu>
In-Reply-To: <20140120163951.7fe4c1f8@calavera>
References:  <20140120163951.7fe4c1f8@calavera>

next in thread | previous in thread | raw e-mail | index | archive | help

Do you have OCZ SSD's?

http://lkcl.net/reports/ssd_analysis.html

Kojedzinszky Richard
Euronet Magyarorszag Informatikai Zrt.

On Mon, 20 Jan 2014, Philipp wrote:

> Date: Mon, 20 Jan 2014 16:39:51 +0100
> From: Philipp <mailinglists@cypresscreek.de>
> To: freebsd-fs@freebsd.org
> Subject: Filesystem errors with VirtIO
> 
> Hi everyone,
>
> I'm running FreeBSD 10.0-RELEASE on a virtualized KVM server. I'm
> using VirtIO from base to access NIC and HDD directly. Filesystem is
> UFS2 with Journaling and SU. Last week I had to reinstall FreeBSD
> because the salvation of the several filesystem errors wasn't possible
> anymore. I don't have any evidence but I guess it has something to do
> with the VirtIO driver.
>
> After running the machine for 48 hours with a freshly installed
> FreeBSD 10 several soft update inconsistencies occur:
>
> # fsck
> ** /dev/vtbd0p2 (NO WRITE)
>
> USE JOURNAL? no
>
> ** Skipping journal, falling through to full fsck
>
> SETTING DIRTY FLAG IN READ_ONLY MODE
>
> UNEXPECTED SOFT UPDATE INCONSISTENCY
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> ADJUST? no
>
> LINK COUNT DIR I=11075332  OWNER=root MODE=40755
> SIZE=512 MTIME=Jan 20 15:06 2014  COUNT 0 SHOULD BE 1
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> ADJUST? no
>
> LINK COUNT DIR I=11316145  OWNER=root MODE=40755
> SIZE=512 MTIME=Jan 20 15:26 2014  COUNT 0 SHOULD BE 1
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> ADJUST? no
>
> UNREF FILE I=11316146  OWNER=root MODE=100644
> SIZE=227096 MTIME=Jan 20 15:26 2014
> CLEAR? no
>
> LINK COUNT DIR I=11316147  OWNER=root MODE=40755
> SIZE=512 MTIME=Jan 20 15:34 2014  COUNT 0 SHOULD BE 1
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> ADJUST? no
>
> LINK COUNT DIR I=11316148  OWNER=root MODE=40755
> SIZE=512 MTIME=Jan 20 15:49 2014  COUNT 0 SHOULD BE 1
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> ADJUST? no
>
> UNREF FILE I=11316150  OWNER=root MODE=100644
> SIZE=928 MTIME=Jan 20 15:49 2014
> CLEAR? no
>
> LINK COUNT DIR I=11333352  OWNER=root MODE=40755
> SIZE=512 MTIME=Jan 20 15:18 2014  COUNT 0 SHOULD BE 1
> LINK COUNT INCREASING
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> ADJUST? no
>
> ** Phase 5 - Check Cyl groups
> 250807 files, 860388 used, 36209947 free (8179 frags, 4525221 blocks,
> 0.0% fragmentation)
>
> After a reboot different inconsistencies appear. I had the very same
> problems with 9.2-RELEASE, which caused the need of a reinstallation
> of the OS (errors like "vtbd0: hard error cmd=write fsbn 24162"
> occured).
>
> Can someone confirm these problems with VirtIO? What else can I do?
>
> Regards, Philipp
> _______________________________________________
> freebsd-fs@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.DEB.2.10.1401201753220.26535>