also sprach martin f krafft [2014-08-05 16:15 +0300]:
> > It's possible that this was caused by a memory corruption, but it
> > wouldn't have been high on my suspect list. Still, if this is
> > a new machine, it might not be a bad idea to run memtest86+ for
> > 24-48 hours.
>
> … and will do tha
also sprach Theodore Ts'o [2014-08-05 14:51 +0200]:
> One likely cause of this issue is that the hardware hiccuped on
> a read, and returned garbage, which is what triggered the "EXT4-fs
> error" message (which is really a report of a detect file system
> inconsistency). A common cause of this is
On Tue, Aug 05, 2014 at 12:34:36PM +0200, martin f krafft wrote:
> Dear kernel people,
>
> Yesterday, I encountered something weird on one of our NAS machines:
>
> Aug 4 20:09:40 julia kernel: [342873.007709] EXT4-fs error (device dm-6):
> ext4_ext_check_inode:481: inode #30414321: comm du: p
Dear kernel people,
Yesterday, I encountered something weird on one of our NAS machines:
Aug 4 20:09:40 julia kernel: [342873.007709] EXT4-fs error (device dm-6):
ext4_ext_check_inode:481: inode #30414321: comm du: pblk 0 bad header/extent:
invalid extent entries - magic f30a, entries 1, max
4 matches
Mail list logo
