Ext4-fs Error Detected Aborted Journal
Contents |
Member Registered: 2009-02-16 Posts: 10 ext4 - "Journal has aborted"? [SOLVED] Hi, recently made ext4 fs error journal has aborted all my partitions use ext4 instead of ext3. Now
Ext4 Fs Error Bad Extra Isize
I might soon find that I'll be regretting it Excerpt from dmesg:ata1.00: exception Emask ext4 fs error raspberry pi 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1.00: status: { DRDY }
Ext3 Fs Error Ext3_journal_start_sb Detected Aborted Journal
ata1: hard resetting link ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: configured for UDMA/133 end_request: I/O error, dev sda, sector 55051824 Aborting journal on device sda2:8. ata1: EH complete sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB) sd 0:0:0:0: [sda] Write ext4_journal_start_sb detected aborted journal redhat Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ext4_abort called. EXT4-fs error (device sda2): ext4_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted EXT4-fs error (device sda2) in ext4_dirty_inode: Journal has aborted mpage_da_map_blocks block allocation failed for inode 164698 at logical offset 47 with max blocks 4 with error -30 This should not happen.!! Data will be lost ext4_da_writepages: jbd2_start: 1024 pages, ino 164698; err -30 Pid: 20, comm: pdflush Tainted: P 2.6.29-ARCH #1 Call Trace: [ Bug #1445195: [Hyper-V] Kernel patches for storvsc. Edit Remove 28 This bug affects 6 people Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit Fix Committed Undecided Unassigned Edit Also affects project (?) Also affects distribution/package Nominate for series Bug Description Because "ubuntu-bug linux" not works because I am on kernel 3.19.0-17, ext4_reserve_inode_write journal has aborted I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 https://bbs.archlinux.org/viewtopic.php?id=70077 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read-only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that https://bugs.launchpad.net/bugs/1456985 the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en-us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5 Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official https://ubuntuforums.org/showthread.php?t=1480014 Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu http://askubuntu.com/questions/767722/14-04-tls-aborting-journal-remounting-filesystem-read-only-how-to-prevent Forum Community Ubuntu Official Flavours Support General Help [ubuntu] sometimes ext4 /home partition remount read-only Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is fs error the place to report it, thanks ! Results 1 to 7 of 7 Thread: sometimes ext4 /home partition remount read-only Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 11th, 2010 #1 frka View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date May 2010 Location Germany Beans 4 DistroUbuntu 10.04 Lucid Lynx sometimes ext4 detected aborted journal /home partition remount read-only Hello! I'm using Ubuntu 10.04 64bit (Kernel 2.6.32-22-generic) and sometimes my /home partition is remounting in read-only and i have no idea why. Normally I only use programms like Firefox, Rhythmbox, Evolution and Netbeans 6.8. What can I do to fix it? Should I switch to the EXT3 filesystem? dmesg shows me the following information: Code: [ 8758.010352] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 8758.010356] ata7.00: failed command: FLUSH CACHE [ 8758.010360] ata7.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 8758.010361] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8758.010363] ata7.00: status: { DRDY } [ 8758.010366] ata7: hard resetting link [ 8758.540045] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8758.550583] ata7.00: configured for UDMA/133 [ 8758.550587] ata7.00: device reported invalid CHS sector 0 [ 8758.550596] ata7: EH complete [ 8758.565414] end_request: I/O error, dev sdb, sector 94076126 [ 8758.565453] Aborting journal on device sdb6-8. [ 8758.657798] EXT4-fs error (device sdb6): ext4_journal_start_sb: Detected aborted journal [ 8758.657803] EXT4-fs (sdb6): Remounting filesystem read-only lspci | grep SATA Code: 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller #1 00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller #2 02:00.0 SATA con communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top 14.04 TLS Aborting Journal / Remounting filesystem read-only - how to prevent? up vote 0 down vote favorite Have ~40 VMs under VMWare/ESXi 5.5 with a guest system Ubuntu 14.04 TLS. About once in 3 weeks one VM goes into read only mode. There's a VMware KB ticket here: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=51306 which contains a workaround (that works), but also suggests to upgrade the OS to 7.10. Since I have 14.04, how can I tell if this is the same kernel issue, if it has been fixed in my version: Linux version 3.13.0-71-generic (buildd@lgw01-09) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 My focus is not on restoring the VM, but on preventing this in the future. Seeing the below in dmesg: =========================== [ 378.085866] Write(10): 2a 00 00 04 a9 b8 00 00 28 00 [ 378.085875] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 58311 (offset 0 size 20480 starting block 38204) [ 378.085879] Buffer I/O error on device sda1, logical block 37943 [ 378.086924] Buffer I/O error on device sda1, logical block 37944 [ 378.087964] Buffer I/O error on device sda1, logical block 37945 [ 378.089046] Buffer I/O error on device sda1, logical block 37946 [ 378.090069] Buffer I/O error on device sda1, logical block 37947 [ 378.090897] sd 2:0:0:0: [sda] [ 378.090898] Result: hExt4_journal_check_start:56: Detected Aborted Journal
Aborting Journal On Device