From owner-freebsd-questions@freebsd.org Sun Jul 26 09:43:22 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E08259ABC7E for ; Sun, 26 Jul 2015 09:43:21 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CC96A44 for ; Sun, 26 Jul 2015 09:43:20 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.erewhon.home ([83.162.243.5]) by smtp-cloud6.xs4all.net with ESMTP id wxi71q00B07iGuj01xi8Qr; Sun, 26 Jul 2015 11:42:08 +0200 Received: by slackbox.erewhon.home (Postfix, from userid 1001) id B8D8F12434; Sun, 26 Jul 2015 11:42:07 +0200 (CEST) Date: Sun, 26 Jul 2015 11:42:07 +0200 From: Roland Smith To: CK Cc: freebsd-questions@freebsd.org Subject: Re: Endless Data Loss Message-ID: <20150726094207.GB81355@slackbox.erewhon.home> Mail-Followup-To: CK , freebsd-questions@freebsd.org References: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2015 09:43:22 -0000 --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 11:33:38PM -0800, CK wrote: > Hi readers, >=20 > In the last 2 years, I have upgraded from 4.11 to 9.2 then 9.3 > releases, and since upgrading to the 9 series, I have experienced > endless data loss - every time I reboot my computer, massive numbers > of files vanish - 20 - 50 - a lot. And it's driving me crazy. > I don't expect to get any fixes here, but something is wrong > with the code - it's happening on ATA drives, USB flash drives, > a few of each kind. So, it's definitely not a hardware problem. I wouldn't be so sure. Your hardware is old. That can cause problems. How did you perform the "upgrade"? Did you keep the old UFS1 partition or d= id you make a backup of your data, wiped the disk and did a full install of 9.= x? (you can check filesystem formats with "dumpfs") Do the problems persist if you boot with the generic kernel? > I wrote about this 2 months ago or so, and was advised to run > a utility on my hard drives - and the utility showed some wear, > but this is happening on USB sticks and cards as well, and > has nothing to do with old ATA drive wear. >=20 > I searched Google for data loss on FreeBSD, and I see that many > others have this problem as well. After 20 years, I am not keen > on switching away from FreeBSD, but the data loss is just killing me. > Every day, I am losing dozens of files. I am backing up, but that > is not the best solution, because it's easy to backup and mirror > the data loss as well, and it's a pain to constantly have the > stress of not knowing if critical files exist or not, and > constantly matching directories/archives to see which are complete > and current. If you have softupdates and journaling enabled, do *not* try to dump a live filesystem. There is a bug that screws things up in this case. Either switch off journaling or go to single user mode and remount the filesystems as read-only before dumping. > PS. One thing I notice is that if I ever ensure correct permissions > of the .sujournal files, but setting them to the same values that > they already have, upon reboot I get an error message to the effect > "timestamp on journal doesn't match last mount time", and then there > is a fallback to a full fsck, most always followed by some cleared > inodes and file loss. If you set the permissions, you access the file, altering the timestamp. *Why* do you think you need to do this? AFAIK, you should not mess with these files! Roland --=20 R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 5753 3324 1661 B0FE 8D93 FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0) --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAABCAAGBQJVtKtvAAoJEED21dyjijPg1XkQAMVphNCGGNlS5rPCSv+tCQBx z2GUn1MQijgXbD4qBVPWltD6Oc8vQP0ZCdrmj0IInhPK8XHCM8/UovArcUcurL3a 8qcut/u6eCBwhnRLW5fPlasvM3F33NTduT/qP6RbtH5IkD8zXcesA5Mk8gXhW24M r6HqZwdW5nwJAxRNjV7vPg8wiHfDHvccipJzT9S9CX7ZT/VBGC4tmMFLLSEUwFhz bU3Li2dCRXffwAr8N+1DaAsXWE9tmLH4Rvrkl8XNroTnNcXZF9sP7Bg4FPfRicjS e4XSjuHJwC5VHICCrPiTl5GVZxpHhttiH5kmSDJmfygs8/1gjLxWhJBP2z3KX1cw meQCXSnceFuD66+E782j/HBVjJyxZh7gA7wY+093EIhFMP8DM+dQ+74arQuuuiYX uYlyxdsOzVS59SAEaWnVxbERY7NvXKCZnn64osguwChS2OqWkcIcuFaAyVT0M/16 Ze712mvTX2NkWOmiI8jBYYsWh+UOkIpAf0ax6o35HInt+EHs7CQBHnh6FQWoj+GK rKI2FNlROJe3MdE3ioQFpZT4UkhSAOqwhuQRHNRnJ9Nh2Ge7myb+eLSBh+m2XHb4 O9QUBsKRvbqQSaJPAXA3Kjw1KLyH9juTov2Yq8Jjuclaiu42gKkajziU/h/V1x0v jCHeUOxzAejjZxjUh7LF =kGcg -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj--