All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205417] Files corruption ( fs/ext4/inode.c:3941 ext4_set_page_dirty+0x3e/0x50 [ext4] )
Date: Mon, 04 Nov 2019 14:32:37 +0000	[thread overview]
Message-ID: <bug-205417-13602-PbXsrOMOmp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205417-13602@https.bugzilla.kernel.org/>

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

Theodore Tso (tytso@mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@mit.edu

--- Comment #1 from Theodore Tso (tytso@mit.edu) ---
Can you send the complete /var/log/messages and/or /var/log/kern.log from say,
a day before the hang up to the hang?

These sorts of issues can be caused by I/O errors and/or other problems in the
device driver and/or device mapper storage stack.   So please also describe
your hardware and storage configuration, and what distribution are you using.

Also, is this a 5.3.8 upstream kernel which you compiled yourself or a
distro-supplied kernel?   If you compiled it yourself, please also send the
kernel config

Thanks!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2019-11-04 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 13:14 [Bug 205417] New: Files corruption ( fs/ext4/inode.c:3941 ext4_set_page_dirty+0x3e/0x50 [ext4] ) bugzilla-daemon
2019-11-04 14:32 ` bugzilla-daemon [this message]
2019-11-04 14:52 ` [Bug 205417] " bugzilla-daemon
2019-11-04 14:55 ` bugzilla-daemon
2019-11-04 15:55 ` bugzilla-daemon
2019-11-04 16:11 ` bugzilla-daemon
2019-11-04 16:12 ` bugzilla-daemon
2019-11-05 21:12 ` bugzilla-daemon
2019-12-18 12:52 ` bugzilla-daemon

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=bug-205417-13602-PbXsrOMOmp@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.