On Mon, Mar 07, 2016 at 11:39:11AM -0700, Chris Murphy wrote: > Since there's no hardware issue suspect, you could filter for just btrfs. > > journalctl -o short-iso | grep -i btrfs Which is exactly what I did. Why did you suspect that my logs were "trimmed"? That's what got me kind of furious. I took great care to not trim relevant information. > When there's hardware stuff suspect it's better to include all the > SCSI and libata (and USB if it's a USB drive) messages also. None there. > If you have any logs that include the filesystem mounted with > enospc_debug, that might be useful for a developer? The later logs I posted were actually taken with enospc_debug, the 4.4.3 ones even with Duncan's patch. I think I didn't apply it before building 4.4.4. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
