[Bug 1072006] [NEW] busybox mount does not accept "-o strictatime"

[Bela Lubkin]

Public bug reported:

The "strictatime" flag is not decoded.  This was fixed recently upstream
in busybox, see https://bugs.busybox.net/show_bug.cgi?id=5240

Significance: I want to debug a boot-time problem by observing which
files have been accessed up to the point of failure during boot.
Therefore I edit /etc/default/grub, adding ``rootflags=strictatime'' to
the GRUB_CMDLINE_LINUX value; and run `update-grub`; and reboot.  Boot
then fails because the root filesystem mount fails.  (Also tested with a
seemingly spurious comma, `rootflags=,strictactime'', which I got from
googling -- no difference.)

Found in an Ubuntu 11.10 system, but verified this is still true in
current 13.04 developmental source.

** Affects: busybox (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1072006

Title:
  busybox mount does not accept "-o strictatime"

Status in “busybox” package in Ubuntu:
  New

Bug description:
  The "strictatime" flag is not decoded.  This was fixed recently
  upstream in busybox, see https://bugs.busybox.net/show_bug.cgi?id=5240

  Significance: I want to debug a boot-time problem by observing which
  files have been accessed up to the point of failure during boot.
  Therefore I edit /etc/default/grub, adding ``rootflags=strictatime''
  to the GRUB_CMDLINE_LINUX value; and run `update-grub`; and reboot.
  Boot then fails because the root filesystem mount fails.  (Also tested
  with a seemingly spurious comma, `rootflags=,strictactime'', which I
  got from googling -- no difference.)

  Found in an Ubuntu 11.10 system, but verified this is still true in
  current 13.04 developmental source.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1072006/+subscriptions