Re: filesystem error

2016-04-22 Thread Gordon Messmer
On 04/22/2016 05:39 AM, Jeffrey Ross wrote: md2 is my root partition, I ran "find / -mount -inum 1308162" find didn't return any value. Using debugfs is faster: # debugfs /dev/md2 debugfs: ncheck 1308162 However, as I understand it, the message you recorded is "strictly for information" htt

Re: filesystem error

2016-04-22 Thread Samuel Sieb
On 04/22/2016 01:04 PM, Jeffrey Ross wrote: Thanks everybody for the suggestions, I figured running fsck would fix it, I should have mentioned that in the past I've attempted to run fsck but it hadn't cleared, probably how I ran it. running fsck -fn /dev/md2 does in fact produce a handful of err

Re: filesystem error

2016-04-22 Thread Jeffrey Ross
> I have the following error reported in my logs, I've had it for quite > some time and through several reboots > > EXT4-fs (md2): error count: 1 > EXT4-fs (md2): initial error at 1452554514: ext4_lookup:1343: inode > 1308162 > EXT4-fs (md2): last error at 1452554514: ext4_lookup:1343: inode 130816

Re: filesystem error

2016-04-22 Thread Chris Murphy
On Fri, Apr 22, 2016 at 1:23 PM, Samuel Sieb wrote: > On 04/22/2016 12:19 PM, Chris Murphy wrote: >> >> On Fri, Apr 22, 2016 at 12:54 PM, Samuel Sieb wrote: >>> >>> e2fsck -fn /dev/sda3 >>> >>> -f to force it, -n to do it-read-only >> >> >> In the OP's example where an md2 device was affected, it

Re: filesystem error

2016-04-22 Thread Samuel Sieb
On 04/22/2016 12:19 PM, Chris Murphy wrote: On Fri, Apr 22, 2016 at 12:54 PM, Samuel Sieb wrote: e2fsck -fn /dev/sda3 -f to force it, -n to do it-read-only In the OP's example where an md2 device was affected, it needs fsck run on /dev/md2 (assembled and running but not mounted). Since md2 i

Re: filesystem error

2016-04-22 Thread Chris Murphy
On Fri, Apr 22, 2016 at 12:54 PM, Samuel Sieb wrote: > On 04/22/2016 07:26 AM, maderios wrote: >> >> On 04/22/2016 02:39 PM, Jeffrey Ross wrote: >>> >>> I have the following error reported in my logs, I've had it for quite >>> some time and through several reboots >>> >>> EXT4-fs (md2): error coun

Re: filesystem error

2016-04-22 Thread Samuel Sieb
On 04/22/2016 07:26 AM, maderios wrote: On 04/22/2016 02:39 PM, Jeffrey Ross wrote: I have the following error reported in my logs, I've had it for quite some time and through several reboots EXT4-fs (md2): error count: 1 EXT4-fs (md2): initial error at 1452554514: ext4_lookup:1343: inode 13081

Re: filesystem error

2016-04-22 Thread Jon LaBadie
On Fri, Apr 22, 2016 at 08:39:05AM -0400, Jeffrey Ross wrote: > I have the following error reported in my logs, I've had it for quite some > time and through several reboots > > EXT4-fs (md2): error count: 1 > EXT4-fs (md2): initial error at 1452554514: ext4_lookup:1343: inode 1308162 > EXT4-fs (m

Re: filesystem error

2016-04-22 Thread maderios
On 04/22/2016 02:39 PM, Jeffrey Ross wrote: I have the following error reported in my logs, I've had it for quite some time and through several reboots EXT4-fs (md2): error count: 1 EXT4-fs (md2): initial error at 1452554514: ext4_lookup:1343: inode 1308162 EXT4-fs (md2): last error at 145255451

filesystem error

2016-04-22 Thread Jeffrey Ross
I have the following error reported in my logs, I've had it for quite some time and through several reboots EXT4-fs (md2): error count: 1 EXT4-fs (md2): initial error at 1452554514: ext4_lookup:1343: inode 1308162 EXT4-fs (md2): last error at 1452554514: ext4_lookup:1343: inode 1308162 md2 is