All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 92501] New: Root filesystem corruption
Date: Mon, 02 Feb 2015 13:45:31 +0000	[thread overview]
Message-ID: <bug-92501-13602@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 92501
           Summary: Root filesystem corruption
           Product: File System
           Version: 2.5
    Kernel Version: 3.17.7 to 3.18.3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: ionut.radu@gmail.com
        Regression: No

Created attachment 165581
  --> https://bugzilla.kernel.org/attachment.cgi?id=165581&action=edit
log containing the filesystem corruptions and kernel version

Description of problem:
I have 3 laptops with Fedora 21, kernel 3.17.7 and all suffered from disk
corruption 
that prevent them to boot at some time.
I have root and home filesystem on the same disk partition. Corruption occurs
for temporary files of chrome and firefox.

Version-Release number of selected component (if applicable):
3.17.7

How reproducible:
All of my 3 laptops suffered from 
this at some time with Fedora 21
and kernel 3.17.7. Never happened before
and suddenly all 3 have filesystem corruption

Steps to Reproduce:
1. Don't know how to reproduce
2.
3.

Actual results:


Expected results:


Additional info:

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

             reply	other threads:[~2015-02-02 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 13:45 bugzilla-daemon [this message]
2016-03-20 12:04 ` [Bug 92501] Root filesystem corruption bugzilla-daemon
2016-03-20 12:04 ` 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-92501-13602@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.