Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 871666 Details for
Bug 1073661
kernel 3.13.5 causes ext4 disk corruption
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
some EXT4-fs error messages during the failure and afterward
ext4-fs error log.txt (text/plain), 7.17 KB, created by
Brian Sipos
on 2014-03-06 22:38:32 UTC
(
hide
)
Description:
some EXT4-fs error messages during the failure and afterward
Filename:
MIME Type:
Creator:
Brian Sipos
Created:
2014-03-06 22:38:32 UTC
Size:
7.17 KB
patch
obsolete
>... > >Mar 6 14:09:03 localhost kernel: [ 14.478736] EXT4-fs (dm-1): warning: mounting fs with errors, running e2fsck is recommended >Mar 6 14:09:03 localhost kernel: [ 14.495714] EXT4-fs (dm-1): re-mounted. Opts: (null) >Mar 6 14:09:03 localhost kernel: [ 17.314396] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) >Mar 6 14:09:03 localhost kernel: [ 17.764909] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) >Mar 6 14:09:03 localhost kernel: [ 17.803976] EXT4-fs error (device dm-1): ext4_free_inode:319: comm systemd-tmpfile: bit already cleared for inode 534082 >Mar 6 14:09:03 localhost kernel: [ 17.823546] EXT4-fs error (device dm-1): ext4_free_inode:319: comm systemd-tmpfile: bit already cleared for inode 534091 >Mar 6 14:09:03 localhost kernel: [ 18.095905] EXT4-fs error (device dm-1): ext4_free_inode:319: comm systemd-tmpfile: bit already cleared for inode 534083 >Mar 6 14:09:03 localhost kernel: [ 18.095962] EXT4-fs error (device dm-1) in __ext4_new_inode:957: IO failure >Mar 6 14:09:03 localhost kernel: [ 18.145291] type=1305 audit(1394132892.184:4): audit_pid=586 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 >Mar 6 14:09:03 localhost kernel: [ 18.241081] JBD2: Spotted dirty metadata buffer (dev = dm-1, blocknr = 0). There's a risk of filesystem corruption in case of system crash. >Mar 6 14:09:03 localhost kernel: [ 18.509233] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:749: group 66, 18448 clusters in bitmap, 601 in gd >Mar 6 14:09:03 localhost kernel: [ 44.502525] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #534079: comm systemd-journal: deleted inode referenced: 540674 >Mar 6 14:09:03 localhost kernel: [ 66.310353] EXT4-fs error (device dm-1) in __ext4_new_inode:957: IO failure >... >Mar 6 14:09:07 localhost kernel: [ 73.727481] EXT4-fs error (device dm-1): ext4_free_inode:319: comm accounts-daemon: bit already cleared for inode 532491 >Mar 6 14:09:07 localhost kernel: [ 73.761260] EXT4-fs error (device dm-1): mb_free_blocks:1308: group 66, block 2186652:freeing already freed block (bit 23964) >... >Mar 6 14:09:07 localhost systemd[1]: Started Daemon for power management. >Mar 6 14:09:08 localhost kernel: [ 74.019273] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm pm-powersave: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost kernel: [ 74.019441] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm pm-powersave: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost kernel: [ 74.019594] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm pm-powersave: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost kernel: [ 74.020585] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm rm: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost kernel: [ 74.020763] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm rm: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost upowerd[1319]: rm: cannot remove â/var/log/pm-powersave.logâ: Input/output error >Mar 6 14:09:08 localhost upowerd[1319]: touch: cannot touch â/var/log/pm-powersave.logâ: Input/output error >Mar 6 14:09:08 localhost upowerd[1319]: /usr/lib64/pm-utils/pm-functions: line 278: /var/log/pm-powersave.log: Input/output error >Mar 6 14:09:08 localhost kernel: [ 74.021636] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm touch: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost kernel: [ 74.021772] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm touch: deleted inode referenced: 532489 >Mar 6 14:09:08 localhost kernel: [ 74.022097] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #533510: comm pm-powersave: deleted inode referenced: 532489 >... >reboot >... >Mar 6 14:16:15 localhost kernel: [ 12.328067] EXT4-fs (dm-1): warning: mounting fs with errors, running e2fsck is recommended >Mar 6 14:16:15 localhost kernel: [ 12.328251] EXT4-fs (dm-1): re-mounted. Opts: (null) >Mar 6 14:16:15 localhost kernel: [ 12.711440] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) >Mar 6 14:16:15 localhost kernel: [ 12.829037] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) >Mar 6 14:16:15 localhost kernel: [ 12.944188] type=1305 audit(1394133162.493:4): audit_pid=581 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 >Mar 6 14:16:15 localhost kernel: [ 13.079113] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:749: group 66, 18447 clusters in bitmap, 601 in gd >Mar 6 14:16:15 localhost kernel: [ 13.096752] JBD2: Spotted dirty metadata buffer (dev = dm-1, blocknr = 0). There's a risk of filesystem corruption in case of system crash. >Mar 6 14:16:15 localhost kernel: [ 29.412281] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #534079: comm journalctl: deleted inode referenced: 540674 >Mar 6 14:16:15 localhost kernel: [ 29.460206] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #534079: comm journalctl: deleted inode referenced: 540674 >Mar 6 14:16:15 localhost kernel: [ 42.351553] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #534079: comm systemd-journal: deleted inode referenced: 540674 >Mar 6 14:16:15 localhost kernel: [ 127.140600] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533992 >Mar 6 14:16:15 localhost kernel: [ 127.141763] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533987 >Mar 6 14:16:15 localhost kernel: [ 127.142882] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533990 >Mar 6 14:16:15 localhost kernel: [ 127.144047] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533996 >Mar 6 14:16:15 localhost kernel: [ 127.145076] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533995 >Mar 6 14:16:15 localhost kernel: [ 127.146146] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533988 >Mar 6 14:16:15 localhost kernel: [ 127.147236] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533993 >Mar 6 14:16:15 localhost kernel: [ 127.148320] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533999 >Mar 6 14:16:15 localhost kernel: [ 127.149363] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533989 >Mar 6 14:16:15 localhost kernel: [ 127.167225] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533991 >Mar 6 14:16:15 localhost kernel: [ 127.168579] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533998 >Mar 6 14:16:15 localhost kernel: [ 127.169726] EXT4-fs error (device dm-1): ext4_free_inode:319: comm rpmdb: bit already cleared for inode 533997 >Mar 6 14:16:15 localhost kernel: [ 223.554251] EXT4-fs error (device dm-1): ext4_lookup:1428: inode #534079: comm systemd-journal: deleted inode referenced: 540674 >... >some more EXT4-fs errors as the system was used/fixed later
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1073661
: 871666