Bug 1198012 - fsck performed when system thaws from hibernation
Summary: fsck performed when system thaws from hibernation
Keywords:
Status: CLOSED DUPLICATE of bug 1174945
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-03 08:33 UTC by Till Maas
Modified: 2015-03-06 10:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-06 10:25:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Till Maas 2015-03-03 08:33:12 UTC
Description of problem:
When I boot my system after hibernation, dracut starts systemd-fsck to fsck the root device and recovers the journal. Afterwards dracut thaws the system from hibernation. This seems to corrupt the root file system as expected.

Version-Release number of selected component (if applicable):
dracut-038-32.git20141216.fc21
systemd-216-20.fc21

How reproducible:
always

Steps to Reproduce:
1. hibernate
2. start system
3. watch console output

Actual results:
fsck is performed

Expected results:
the file systems are left alone

Additional info:

Comment 1 Harald Hoyer 2015-03-06 10:14:57 UTC
see
https://bugzilla.redhat.com/show_bug.cgi?id=1174945#c7
and
https://bugzilla.redhat.com/show_bug.cgi?id=1174945#c8

Seems like it is fixed for recent systemd and dracut versions.

I should backport the fix, though.

Comment 2 Till Maas 2015-03-06 10:25:22 UTC
(In reply to Harald Hoyer from comment #1)
> see
> https://bugzilla.redhat.com/show_bug.cgi?id=1174945#c7
> and
> https://bugzilla.redhat.com/show_bug.cgi?id=1174945#c8
> 
> Seems like it is fixed for recent systemd and dracut versions.
> 
> I should backport the fix, though.

thank you for the information. However file system corruption bugs like should should IMHO get higher priority in the future, especially considering that a patch was available for several months.

*** This bug has been marked as a duplicate of bug 1174945 ***


Note You need to log in before you can comment on or make changes to this bug.