Latest kernel in F20 leads to read only file system

Kyle McMartin kyle at redhat.com
Thu Feb 20 03:31:03 UTC 2014


On Wed, Feb 19, 2014 at 10:19:16PM -0700, Erinn Looney-Triggs wrote:
> On 2/19/2014 6:36 PM, Eric Sandeen wrote:
> >On 2/19/14, 6:02 PM, Erinn Looney-Triggs wrote:
> >>kernel-3.13.3-201.fc20.x86_64 seems to lead to file system failures
> >>for me. Kernels < 3.13 however do not have this issue.
> >>
> >>At first I thought it was just file system corruption. However, after
> >>approximately 5 reinstalls today the issue continues to surface every
> >>time I move to the 3.13 kernel, whether using BTRFS or ext4.
> >>
> >>Behavior for both file systems differs slightly, ext4 complains about
> >>a fair number of errors (sorry I don't have the specifics)
> >We'll need those specifics.  ;)  dmesg and/or kernel logs in a bugzilla
> >would probably be best.
> >
> >-Eric
> >
> 
> Ok given that I don't have a writeable file system, is there any
> reasonably smart way to go about getting these error messages to you
> other than writing them down and typing them up?
> 

You could just pipe dmesg to fpaste?

dmesg | fpaste should still work on an ro root fs.

--kyle


More information about the kernel mailing list