Bug 904235

Summary:	partitioner does not preserve noatime on btrfs
Product:	[openSUSE] openSUSE Distribution	Reporter:	Olaf Hering <ohering>
Component:	YaST2	Assignee:	YaST Team <yast-internal>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	aschnell
Version:	13.2
Target Milestone:	---
Hardware:	x86-64
OS:	Linux
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Olaf Hering 2014-11-06 15:53:01 UTC

13.2 in a gen1 hyperv guest

I tried to mount the proposed btrfs root partition with by-label and also set the noatime flag. Everytime I return to the "detailed window" the noatime checkbox is off again.
Maybe btrfs does not support noatime? If so, the checkbox should not be offered.

Comment 1 Ancor Gonzalez Sosa 2014-11-10 17:37:31 UTC

In fact, the flag is internally preserved. So if you set the noatime flag, the partition will be configured to be mounted with noatime. The problem is that the representation of the information used in the user interface is not updated according to the internal representation.

What follows is the result of my findings, so libstorage developer (already in CC) can fix the bug or point me in the right direction).

As said. The call to Volume::changeFstabOptions succeeds. But immediately afterwards, the Ruby code calls getPartitionInfo. In other tests without Btrfs involved, the resulting partitioninfo.v.fstab_options contains the new information (the one set by changeFstabOptions). But apparently, when the system is in Btrfs, after calling getPartitionInfo the old value is found in partitioninfo.v.fstab_options.

My shot in the dark was to take a look to [1] vs [2]. But I see no obvious difference in how the volume is handled there. I guess the failure does nothing to do with those functions (as said, just a shot in the dark).

[1] https://github.com/openSUSE/libstorage/blob/d7637db4727f8e1db4bd4558f622e303116e0f8c/storage/Partition.cc#L610
[2] https://github.com/openSUSE/libstorage/blob/df351c947980a5cd10f8d72b623a58327f6a30ef/storage/Btrfs.cc#L933

Comment 2 Arvin Schnell 2014-11-11 09:41:33 UTC

I will look at it when time permits.

Comment 3 Arvin Schnell 2015-07-10 13:17:54 UTC

Sorry, but I could not pin point the issue within an hour. So I added a card
to the YaST trello task board so that the issue is prioritisedwith the other
tasks.

Comment 4 Tomáš Chvátal 2018-04-12 13:52:34 UTC

This version of openSUSE changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE, or consider the bug still valid, please feel free to reopen this
bug against that version, or open a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime