From owner-freebsd-bugs@freebsd.org Mon Jun 17 12:20:31 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16A9315B7FE4 for ; Mon, 17 Jun 2019 12:20:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9BD078DD42 for ; Mon, 17 Jun 2019 12:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5C2CA15B7FDE; Mon, 17 Jun 2019 12:20:30 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FA3D15B7FDD for ; Mon, 17 Jun 2019 12:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFC978DD41 for ; Mon, 17 Jun 2019 12:20:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0077F555B for ; Mon, 17 Jun 2019 12:20:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x5HCKSYx035344 for ; Mon, 17 Jun 2019 12:20:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x5HCKQ75035331 for bugs@FreeBSD.org; Mon, 17 Jun 2019 12:20:26 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238663] [UFS] Corrupted files since migration to FreeBSD11 Date: Mon, 17 Jun 2019 12:20:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nicolas.masse@stormshield.eu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 12:20:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238663 Bug ID: 238663 Summary: [UFS] Corrupted files since migration to FreeBSD11 Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: nicolas.masse@stormshield.eu Since we migrated from FreeBSD-10 to FreeBSD11, we see that some files get corrupted. We were able to reproduce the issue by running a script with the following scenario: - mount the filesystem read-write with the -async flag - decompress some archives - unmount the filesystem - remount the filesystem readonly Once we do that, we generally see one or two files being corrupted. Note that this only happens when using some recents SSD. Also note that unmounting the filesystem is necessary to see the problem. W= hen accessing the files before the umount command, they all seems ok. AFAICS, this looks like as if one page was loaded in memory, but wasn't wri= tten physically on the disk. Here is a shortned version of the script I am using: #!/bin/sh mount -o async $PARTITION /mnt/disk tar --no-same-owner -C /mnt/disk/new_dir -zxUf archive1.tgz 7zr x -y -bd -o/mnt/disk ./archive2.7z 7zr x -y -bd -o/mnt/disk ./archive3.7z mv /mnt/disk/dir /mnt/disk/old_dir mv /mnt/disk/new_dir /mnt/disk/dir rm -rf /mnt/disk/old_dir umount $MAJ_PARTITION /mnt/disk/ mount -o ro $MAJ_PARTITION /mnt/disk/ check_integrity # here we check the md5 of the decompressed files The filesystem use the following tunings: SNI40A16C0818A9>tunefs -p /dev/ufs/disk tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 2616 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) main --=20 You are receiving this mail because: You are the assignee for the bug.=