On Fri, Aug 22, 2014 at 12:32:27PM -0500, Eric Sandeen wrote:
> On 8/22/14, 10:50 AM, Marc MERLIN wrote:
>
> > But if my kernel hangs due to a bug that isn't btrfs' fault and I need
> > to power off and back on, after reboot my google-chrome profile is
> > almost always broken in some way.
>
> Given my experiences with userspace in general, I'd lay money on
> google-chrome simply not DTRT WRT data integrity syscalls (or
> maybe it's the sqlite database handling underneath...)
>
> Does it behave any differently on other filesystems?
Well
1) I used to work on chromeos until some months back, and haven't heard
on this problem with chrome/linux
2) never had a chrome corruption problem on a non btrfs filesystem
3) as mentioned, my btrfs snapshots are somehow always consistent for
chrome, which if chrome were not flushing its buffers right, wouldn't
happen.
Incidently, I just had to rebuild my mysqldb on my laptop after it got
corrupted in a way that was non recoverable.
Mysql surely knows how to flush and have consistent state points.
In my experience, linux crashes cause btrfs to somehow end up with non
consistent states on disk. Whether it's a bug in the btrfs code, the
linux block subsystem or sata driver, or firmware bugs on all 5 SSDs
I've had so far, I can't say, but there is a problem somewhere for sure.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
