Date: Thu, 20 Jun 2019 14:27:13 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 238663] [UFS] Corrupted files since migration to FreeBSD11 Message-ID: <bug-238663-3630-jJPH7QDGgB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238663-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-238663-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238663 --- Comment #3 from Masse Nicolas <nicolas.masse@stormshield.eu> --- In fact I can't give you the file I ran my tests with, but fortunately I was able to reproduce the issue with the archive llvm50-5.0.2_1.txz from pkg (t= ook that one because it was on my computer). I also update my scripts in order to have something more generic, so that I= can attach them to this issue. Here is how I did reproduce: - grab the file https://pkg.freebsd.org/FreeBSD:10:amd64/latest/All/llvm50-5.0.2_1.txz (oth= er archives should work too, but this is the one I used for my tests) - untar the archive and generate the md5 file using the script compute_md5.= sh - copy the tar/md5 files on a specific device* - run the test in loop using the command "./test_disk.sh llvm50-5.0.2_1.txz /dev/<my_partition> md5_llvm5.txt" * only devices with a recent SSD did show the problem The number of retry to have the problem may vary from 3 up to more than 20 attempts (my last run got one corrupted file after 33 attempts). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238663-3630-jJPH7QDGgB>