From mboxrd@z Thu Jan 1 00:00:00 1970 From: Liam Subject: Re: kernel oops -> no mount (different problem than others) Date: Sat, 20 Aug 2011 01:53:39 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-btrfs@vger.kernel.org To: cwillu Return-path: In-Reply-To: List-ID: Thanks for your help, but unfortunately, it wouldn't mount read-only, either. If you can think of anything else I could try, it would be greatly appreciated! Thanks! - Liam On Thu, Aug 18, 2011 at 8:52 PM, cwillu wrote: > You might try mounting it "-o ro" as a stopgap to regain readonly acc= ess. > > Judging from the bootlog, the error itself appears to be enospc. =A0I= n > which case there's no already-available quick fix; I expect a > developer to chime in any second now :p > >> From the logs it is listing a transid error but NOT that it is >> expecting a different one, simply >> >> device label 1TB devid 1 transid 248472 /dev/sdb > > That particular line is the normal listing of devices, which is > expected and completely normal. > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html