From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail2.candelatech.com ([208.74.158.173]) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gGXDQ-0002G8-8I for linux-mtd@lists.infradead.org; Sat, 27 Oct 2018 22:37:57 +0000 Subject: Re: read-only FS with error -2 To: Richard Weinberger References: <14ebdb35-43e6-47b6-e947-2d9f9cee100b@candelatech.com> Cc: "linux-mtd @ lists . infradead . org" From: Ben Greear Message-ID: <5400505c-8f52-da00-e607-cf0b68a1f93f@candelatech.com> Date: Sat, 27 Oct 2018 15:37:33 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/27/2018 01:36 PM, Richard Weinberger wrote: > Ben, > > On Fri, Oct 26, 2018 at 8:39 PM Ben Greear wrote: >> >> Hello, >> >> I did something to my OpenWRT system (running 4.14.78 + 4.19 backports kernel), > > What did you do? :) Well, I created 64 station vdevs on an ath10k NIC, which if nothing else, was hitting a zillion WARN_ON bugs in the mac80211 stack. That flooded dmesg so I don't know if there were any more serious bugs earlier on. >> and it went read-only. Upon reboot, it is still read-only. Is there something >> I can to do debug and/or fix this? >> >> root@LF-R7800-6ab8:/home/lanforge# dmesg|grep -i ubif >> [ 11.595662] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 143 >> [ 11.674298] UBIFS (ubi0:1): recovery needed >> [ 12.028518] UBIFS (ubi0:1): recovery completed >> [ 12.028598] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data" >> [ 12.031847] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes >> [ 12.039815] UBIFS (ubi0:1): FS size: 83042304 bytes (79 MiB, 654 LEBs), journal size 4190208 bytes (3 MiB, 33 LEBs) >> [ 12.049711] UBIFS (ubi0:1): reserved for root: 3922293 bytes (3830 KiB) >> [ 12.059957] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 036CCB1F-5608-4069-B5A0-D22544398634, small LPT model >> [ 12.085050] mount_root: switching to ubifs overlay >> [ 31.942522] UBIFS error (ubi0:1 pid 570): ubifs_iget: failed to read inode 1623, error -2 > > Hmm, UBIFS is unable to find a inode on your MTD. > Can you please mount UBIFS again with "/sys/kernel/debug/ubifs/chk_fs" set to 1? > This will run a self-check and give us maybe more details. > > Did you see in the past odd logs? ECC errors or such? I reinstalled already, and the problem went away. How exactly would I do that test above? The root file system is RO on bootup in the problem case...would I remount root after twiddling the debugfs flag? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com