linux-ext4 - [Bug 89621] EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-89621-13602-6bAKC50yCt@https.bugzilla.kernel.org/>
Date:	Mon, 15 Dec 2014 22:27:11 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 89621] EXT4-fs error (device dm-1):
 ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32

https://bugzilla.kernel.org/show_bug.cgi?id=89621

--- Comment #5 from Theodore Tso <tytso@....edu> ---
Yes, barriers are enabled by default, and with cache=none, the flush commands
*should* be sent down to the host device.   It might be worth doing a quick
blktrace to make sure the host device is getting the cache flushes and they
aren't getting dropped by qemu or by mdraid, but the configuration at least
looks sane.

In the cases where you've seen the problem, have there been any sense where
either (a) the host has suffered a crash or shutdown or power drop, or (b) the
guest VM has been abruptly shutdown or killed without triggering a normal guest
OS shutdown?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html