Bug 901834

Summary:	Snapper corruption causes read-only filesystem and zypper failure
Product:	[openSUSE] openSUSE Distribution	Reporter:	Atri Bhattacharya <badshah400>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	aschnell, chcao
Version:	13.2 RC 1
Target Milestone:	---
Hardware:	64bit
OS:	openSUSE 13.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	save_y2logs

Description Atri Bhattacharya 2014-10-18 11:42:54 UTC

I am guessing that at some point, a zypper up transaction (which seems to automatically call snapper) must have led to some corruption. All I can see is that every time I run snapper/zypper in now systemd-journal causes the filesystem to become read-only and all applications start crashing. A large number of messages are print to tty1 all resembling:

systemd-journal: Failed to truncate file to its own size: Read only filesystem.

The last known successful zypper transaction was updating from kernel 3.17.0 to kernel 3.17.1 (from Kernel:Stable obs project). I don't know what logs to submit that will help, but please let me know. For now, I will likely have to do 
rpm -evh zypper-snapper-plugin
so that at least zypper can run without calling snapper and therefore killing my system.

Comment 1 Atri Bhattacharya 2014-10-18 11:50:26 UTC

Created attachment 610580 [details]
save_y2logs

Sorry in the above I meant "rpm -evh snapper-zypp-plugin" and here is the yast log tarball.

Comment 2 Chenzi Cao 2015-01-12 10:57:27 UTC

Hi Arvin, would you please kindly help to have a look at here? I'm not sure whether it its right to assign it to you. Please feel free to reassign whenever necessary, thank you!

Comment 3 Arvin Schnell 2015-01-12 11:31:54 UTC

Snapper does not set the root filesystem to read-only. AFAIK the kernel
does that for certain filesystem errors so I would look there. The output
of dmesg (or whatever that's called with systemd) might be useful.

Comment 4 Atri Bhattacharya 2015-01-12 15:50:24 UTC

Sorry, should have updated my report: this (rather infamous) problem has been solved since kernel 3.17.2 (see commit [1]), and I myself have not experienced any issues since installing 3.17.2 from Kernel:Stable.

[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.17.y&id=0bd77290116d6bbbeaf173037eddbeea44c66ea1

Comment 5 Arvin Schnell 2015-01-12 15:55:09 UTC

Thanks for the feedback, setting to fixed.