From: Kenneth Johansson <ken@kenjo.org>
To: linux-nfs@vger.kernel.org
Subject: Re: nfs home directory and google chrome.
Date: Wed, 28 Oct 2020 00:01:28 +0100 [thread overview]
Message-ID: <df1c5127-4e48-672f-e2c4-4ce31f146952@kenjo.org> (raw)
In-Reply-To: <0ba0cd0c-eccd-2362-9958-23cd1fa033df@kenjo.org>
So this is just an update to how to avoid this problem.
I switched to nfs v3 and no more issues. Since the switch chrome have
not stopped syncing with the google server even once. suspend resume
causes no issues and everything looks ok. So it's clear that
google-chrome currently does not like nfs v4 and I need chrome to work
more than I need to run nfs v4.
On 2020-10-04 13:53, Kenneth Johansson wrote:
> So I have had for a long time problems with google chrome and suspend
> resume causing it to mangle its sqlite database.
>
> it looks to only happen if I use nfs mounted home directory. I'm not
> sure exactly what is happening but lets first see if this happens to
> anybody else.
>
> How to get the error.
>
> 1. start google from a terminal with "google-chrome"
>
> 2. suspend the computer
>
> 3. wait a while. There is some type of minimum time here I do not know
> what its is but I basically get the error every time of I suspend in
> evening and resume in morning
>
> 4. look for printout that looks like something like this
>
> [16789:18181:1004/125852.529750:ERROR:database.cc(1692)] Passwords
> sqlite error 1034, errno 5: disk I/O error, sql: COMMIT
> [16789:16829:1004/125852.529744:ERROR:database.cc(1692)] Web sqlite
> error 1034, errno 5: disk I/O error, sql: COMMIT
> [16789:16829:1004/125852.530261:ERROR:database.cc(1692)] Web sqlite
> error 1034, errno 5: disk I/O error, sql: INSERT OR REPLACE INTO
> autofill_model_type_state (model_type, value) VALUES(?,?)
> [16789:16789:1004/125852.563571:ERROR:sync_metadata_store_change_list.cc(34)]
> Autofill datatype error was encountered: Failed to update ModelTypeState.
> [16789:19002:1004/125902.534103:ERROR:database.cc(1692)] History
> sqlite error 1034, errno 5: disk I/O error, sql: COMMIT
> [16789:19002:1004/125902.536903:ERROR:database.cc(1692)] Thumbnail
> sqlite error 778, errno 5: disk I/O error, sql: COMMIT
>
>
> [16789:19002:1004/130044.120379:ERROR:database.cc(1692)] Passwords
> sqlite error 1034, errno 5: disk I/O error, sql: INSERT OR REPLACE
> INTO sync_model_metadata (id, model_metadata) VALUES(1, ?)
> [16789:16829:1004/130044.120388:ERROR:database.cc(1692)] Web sqlite
> error 1034, errno 5: disk I/O error, sql: INSERT OR REPLACE INTO
> autofill_model_type_state (model_type, value) VALUES(?,?)
>
>
> and so on. if you use google sync you can also check
> "chrome://sync-internals" to see if something is wrong with the database.
>
>
>
next prev parent reply other threads:[~2020-10-27 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 11:53 nfs home directory and google chrome Kenneth Johansson
2020-10-05 16:46 ` Patrick Goetz
2020-10-05 20:07 ` Kenneth Johansson
2020-10-06 18:14 ` J. Bruce Fields
2020-10-07 10:54 ` Kenneth Johansson
2020-10-07 13:10 ` J. Bruce Fields
2020-10-07 14:34 ` Frank Filz
2020-10-07 15:17 ` 'J. Bruce Fields'
2020-10-07 15:39 ` Chuck Lever
2020-10-07 18:11 ` Frank Filz
2020-10-07 18:36 ` Chuck Lever
2020-10-07 23:58 ` Rick Macklem
2020-10-07 21:10 ` Kenneth Johansson
2020-10-27 23:01 ` Kenneth Johansson [this message]
2020-10-29 17:36 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df1c5127-4e48-672f-e2c4-4ce31f146952@kenjo.org \
--to=ken@kenjo.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).