7:48 p.m.
Hi William,
Thank you for your answer.
I use a bare metal install updated with Clear Linux rev. 8210.
Here is the list of the currently installed bundles:
```
ls -1 /usr/share/clear/bundles
bootloader
dev-utils
editors
file-utils
internet-console-utils
kernel-native
kvm-host
libX11client
network-basic
network-proxy-client
os-core
os-core-update
os-utils
os-utils-gui
python-basic
sysadmin-basic
xfce4-desktop
```
The problem occurs with `noatime` option within the `rootflags=`
settings added in any of the three `Clear-linux-native-4.5.4-2XX.conf`
files currently present in `/boot/loader/entries/` directory.
So here is what I've done so far:
1. edit any of the `Clear-linux-native-4.5.4-2XX.conf` files currently
present in `/boot/loader/entries/` directory, only adding the
`rootflags=noatime` parameter:
```
options console=tty0 console=ttyS0,115200n8 quiet [...]
rootfstype=ext4,btrfs,xfs rootflags=noatime rw [...]
```
2. reboot
3. this results in a kernel panic:
```
[...] Error: unrecognized mount option 'noatime' or missing value
[...]
[...] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-> > block(8,3)
```
Regards,
-- Ben
On Mon, 2016-05-16 at 16:16 -0700, Douglas, William wrote:
Could you include your configuration used to boot the
system? Or
maybe
describe what you did to add/change parameters?
On Mon, May 16, 2016 at 4:04 PM, fb.dev.clx <fb.dev.clx(a)gmail.com>
wrote:
>
> Hi all,
>
> As I wanted to experiment a few kernel parameters on a bare metal
> install, this resulted in a kernel panic with `rootflags=noatime`
> passed in `/boot/loader/entries/Clear-linux-native-*.conf` file:
>
> ```
> Error: unrecognized mount option 'noatime' or missing value
> [...]
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-
> block(8,3)
>
> ```
>
> Any suggestion?
>
> -- Ben
> _______________________________________________
> Dev mailing list
> Dev(a)lists.clearlinux.org
> https://lists.clearlinux.org/mailman/listinfo/dev
8:06 p.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
Hi Ben
Let me try to reproduce it. What HW are you ussing?
Regards
On May 16, 2016 6:48 PM, "fb.dev.clx" <fb.dev.clx(a)gmail.com> wrote:
Hi William,
Thank you for your answer.
I use a bare metal install updated with Clear Linux rev. 8210.
Here is the list of the currently installed bundles:
```
ls -1 /usr/share/clear/bundles
bootloader
dev-utils
editors
file-utils
internet-console-utils
kernel-native
kvm-host
libX11client
network-basic
network-proxy-client
os-core
os-core-update
os-utils
os-utils-gui
python-basic
sysadmin-basic
xfce4-desktop
```
The problem occurs with `noatime` option within the `rootflags=`
settings added in any of the three `Clear-linux-native-4.5.4-2XX.conf`
files currently present in `/boot/loader/entries/` directory.
So here is what I've done so far:
1. edit any of the `Clear-linux-native-4.5.4-2XX.conf` files currently
present in `/boot/loader/entries/` directory, only adding the
`rootflags=noatime` parameter:
```
options console=tty0 console=ttyS0,115200n8 quiet [...]
rootfstype=ext4,btrfs,xfs rootflags=noatime rw [...]
```
2. reboot
3. this results in a kernel panic:
```
[...] Error: unrecognized mount option 'noatime' or missing value
[...]
[...] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-> > block(8,3)
```
Regards,
-- Ben
On Mon, 2016-05-16 at 16:16 -0700, Douglas, William wrote:
Could you include your configuration used to boot
the system? Or
maybe
describe what you did to add/change parameters?
On Mon, May 16, 2016 at 4:04 PM, fb.dev.clx <fb.dev.clx(a)gmail.com>
wrote:
>
> Hi all,
>
> As I wanted to experiment a few kernel parameters on a bare metal
> install, this resulted in a kernel panic with `rootflags=noatime`
> passed in `/boot/loader/entries/Clear-linux-native-*.conf` file:
>
> ```
> Error: unrecognized mount option 'noatime' or missing value
> [...]
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-
> block(8,3)
>
> ```
>
> Any suggestion?
>
> -- Ben
> _______________________________________________
> Dev mailing list
> Dev(a)lists.clearlinux.org
> https://lists.clearlinux.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.clearlinux.org
https://lists.clearlinux.org/mailman/listinfo/dev
8:09 p.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
Hi
>> As I wanted to experiment a few kernel
parameters on a bare metal
>> install, this resulted in a kernel panic with `rootflags=noatime`
>> passed in `/boot/loader/entries/Clear-linux-native-*.conf` file:
The way to use noatime is by using /etc/fstab
>>
>> Any suggestion?
Please create the file /etc/fstab adding the option "noatime"
i.e.
# <file system> <mount point> <type> <options>
<dump> <pass>
/dev/YOUR_ROOT_DEV / ext4 defaults,noatime 0 1
Then reboot your system, and your will find:
/dev/YOUR_ROOT_DEV on / type ext4 (rw,noatime,data=ordered)
--
Regards,
Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation
8:48 p.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
Hi Miguel,
Thank you for your answer.
The way to use noatime is by using /etc/fstab
I am just puzzled by this as the description of `rootflags`
specifically says that it allows you to "give options pertaining to the
mounting of the root filesystem just as you would to the mount
program". So if it is accepted by `mount` it should also be accepted by
`rootflags`.
Therefore, the bug is either in the implementation or in the
documentation...
Also, as `/etc/fstab` is only accessible when root filesystem is
already mounted, adding `noatime` in this file means that the
filesystem should be remounted during the boot process to get the
wanted option(s).
What do you think?
-- Ben
On Mon, 2016-05-16 at 19:09 -0500, Miguel Bernal Marin wrote:
> Hi
>
> >
> > >
> > > >
> > > > As I wanted to experiment a few kernel parameters on a bare
> > > > metal
> > > > install, this resulted in a kernel panic with
> > > > `rootflags=noatime`
> > > > passed in `/boot/loader/entries/Clear-linux-native-*.conf`
> > > > file:
The way to use noatime is by using /etc/fstab
>
> >
> > >
> > > >
> > > >
> > > > Any suggestion?
> Please create the file /etc/fstab adding the option "noatime"
>
> i.e.
>
> # <file system> <mount
> point> <type> <options> <dump> <pass>
> /dev/YOUR_ROOT_DEV / ext4 defaults,noatime 0 1
>
>
> Then reboot your system, and your will find:
>
> /dev/YOUR_ROOT_DEV on / type ext4 (rw,noatime,data=ordered)
>
>
>
>
9:45 p.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
Miguel,
Reading further, it appears to be impossible to set any of the fs-
independent flags via `rootflags`, which explains the special case code
for the `ro` and `rw`.
It is suggested that using an initrd/initramfs to mount the rootfs
instead could work around it.
So, when booting without an initramfs, it seems there is no way to pass
fs-independent flags for the rootfs at boot time. Therefore,
`/etc/fstab` and a remount of the rootfs are required until any other
option exists...
-- Ben
On Mon, 2016-05-16 at 19:48 -0500, fb.dev.clx wrote:
Hi Miguel,
Thank you for your answer.
The way to use noatime is by using /etc/fstab
I am just puzzled by this as the
description of `rootflags`
specifically says that it allows you to "give options pertaining to
the
mounting of the root filesystem just as you would to the mount
program". So if it is accepted by `mount` it should also be accepted
by
`rootflags`.
Therefore, the bug is either in the implementation or in the
documentation...
Also, as `/etc/fstab` is only accessible when root filesystem is
already mounted, adding `noatime` in this file means that the
filesystem should be remounted during the boot process to get the
wanted option(s).
What do you think?
-- Ben
On Mon, 2016-05-16 at 19:09 -0500, Miguel Bernal Marin wrote:
>
> Hi
>
> >
> >
> > >
> > >
> > > >
> > > >
> > > > As I wanted to experiment a few kernel parameters on a bare
> > > > metal
> > > > install, this resulted in a kernel panic with
> > > > `rootflags=noatime`
> > > > passed in `/boot/loader/entries/Clear-linux-native-*.conf`
> > > > file:
> The way to use noatime is by using /etc/fstab
>
> >
> >
> > >
> > >
> > > >
> > > >
> > > >
> > > > Any suggestion?
> Please create the file /etc/fstab adding the option "noatime"
>
> i.e.
>
> # <file system> <mount
> point> <type> <options> <dump> <pass>
> /dev/YOUR_ROOT_DEV / ext4 defaults,noatime 0
> 1
>
>
> Then reboot your system, and your will find:
>
> /dev/YOUR_ROOT_DEV on / type ext4 (rw,noatime,data=ordered)
>
>
> 
10:01 p.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
On 5/16/2016 6:45 PM, fb.dev.clx wrote:
Miguel,
Reading further, it appears to be impossible to set any of the fs-
independent flags via `rootflags`, which explains the special case code
for the `ro` and `rw`.
It is suggested that using an initrd/initramfs to mount the rootfs
instead could work around it.
So, when booting without an initramfs, it seems there is no way to pass
fs-independent flags for the rootfs at boot time. Therefore,
`/etc/fstab` and a remount of the rootfs are required until any other
option exists...
if you have /etc/fstab..
all you need is
mount -o remount,noatime /
(well you don't even need fstab for that ;-)
12:01 a.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
Exactly,
Another good explanation could be found in:
https://bugzilla.kernel.org/show_bug.cgi?id=61601#c10
On 5/16/2016 8:45 PM, fb.dev.clx wrote:
Miguel,
Reading further, it appears to be impossible to set any of the fs-
independent flags via `rootflags`, which explains the special case code
for the `ro` and `rw`.
Yes :D
It is suggested that using an initrd/initramfs to
mount the rootfs
instead could work around it.
And in Clear Linux would like to avoid initrd/initramfs
So, when booting without an initramfs, it seems there
is no way to pass
fs-independent flags for the rootfs at boot time. Therefore,
`/etc/fstab` and a remount of the rootfs are required until any other
option exists...
Yes and the remount is automatically when booting.
-- Ben
On Mon, 2016-05-16 at 19:48 -0500, fb.dev.clx wrote:
--
Regards,
Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation
Hi Miguel,
Thank you for your answer.
The way to use noatime is by using /etc/fstab
I am just puzzled by this as the
description of `rootflags`
specifically says that it allows you to "give options pertaining to
the
mounting of the root filesystem just as you would to the mount
program". So if it is accepted by `mount` it should also be accepted
by
`rootflags`.
Therefore, the bug is either in the implementation or in the
documentation...
Also, as `/etc/fstab` is only accessible when root filesystem is
already mounted, adding `noatime` in this file means that the
filesystem should be remounted during the boot process to get the
wanted option(s).
What do you think?
-- Ben
On Mon, 2016-05-16 at 19:09 -0500, Miguel Bernal Marin wrote:
>
> Hi
>
>>
>>
>>>
>>>
>>>>
>>>>
>>>> As I wanted to experiment a few kernel parameters on a bare
>>>> metal
>>>> install, this resulted in a kernel panic with
>>>> `rootflags=noatime`
>>>> passed in `/boot/loader/entries/Clear-linux-native-*.conf`
>>>> file:
> The way to use noatime is by using /etc/fstab
>
>>
>>
>>>
>>>
>>>>
>>>>
>>>>
>>>> Any suggestion?
> Please create the file /etc/fstab adding the option "noatime"
>
> i.e.
>
> # <file system> <mount
> point> <type> <options> <dump> <pass>
> /dev/YOUR_ROOT_DEV / ext4 defaults,noatime 0
> 1
>
>
> Then reboot your system, and your will find:
>
> /dev/YOUR_ROOT_DEV on / type ext4 (rw,noatime,data=ordered)
>
>
>
8:02 a.m.
New subject: [Dev] Kernel panic when passing noatime in bootargs on bare metal install
Miguel,
Another good explanation could be found in:
https://bugzilla.kernel.org/show_bug.cgi?id=61601#c10>gt;;
It's really a shame I didn't find this sooner...
Well, thank you very much for your time and all your explanations!
-- Ben
On Mon, 2016-05-16 at 23:01 -0500, Miguel Bernal Marin wrote:
Exactly,
Another good explanation could be found in:
https://bugzilla.kernel.org/show_bug.cgi?id=61601#c10
On 5/16/2016 8:45 PM, fb.dev.clx wrote:
Miguel,
Reading further, it appears to be impossible to set any of the fs-
independent flags via `rootflags`, which explains the special case
code
for the `ro` and `rw`.
Yes :D
It is suggested that using an initrd/initramfs to mount the rootfs
instead could work around it.
And in Clear Linux would like to avoid initrd/initramfs
So, when booting without an initramfs, it seems there is no way to
pass
fs-independent flags for the rootfs at boot time. Therefore,
`/etc/fstab` and a remount of the rootfs are required until any
other
option exists...
Yes and the remount is automatically when booting.
>
> -- Ben
>
>
>
>
> On Mon, 2016-05-16 at 19:48 -0500, fb.dev.clx wrote:
> >
> > Hi Miguel,
> >
> > Thank you for your answer.
> >
> > >
> > >
> > > The way to use noatime is by using /etc/fstab
> > I am just puzzled by this as the description of `rootflags`
> > specifically says that it allows you to "give options pertaining
> > to
> > the
> > mounting of the root filesystem just as you would to the mount
> > program". So if it is accepted by `mount` it should also be
> > accepted
> > by
> > `rootflags`.
> > Therefore, the bug is either in the implementation or in the
> > documentation...
> > Also, as `/etc/fstab` is only accessible when root filesystem is
> > already mounted, adding `noatime` in this file means that the
> > filesystem should be remounted during the boot process to get the
> > wanted option(s).
> >
> > What do you think?
> >
> > -- Ben
> >
> >
> > On Mon, 2016-05-16 at 19:09 -0500, Miguel Bernal Marin wrote:
> > >
> > >
> > > Hi
> > >
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > As I wanted to experiment a few kernel parameters on a
> > > > > > bare
> > > > > > metal
> > > > > > install, this resulted in a kernel panic with
> > > > > > `rootflags=noatime`
> > > > > > passed in `/boot/loader/entries/Clear-linux-native-
> > > > > > *.conf`
> > > > > > file:
> > > The way to use noatime is by using /etc/fstab
> > >
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Any suggestion?
> > > Please create the file /etc/fstab adding the option "noatime"
> > >
> > > i.e.
> > >
> > > # <file system> <mount
> > >
point> <type> <options> <dump> <pass>
> > > /dev/YOUR_ROOT_DEV / ext4 defaults,noatime 0
> > > 1
> > >
> > >
> > > Then reboot your system, and your will find:
> > >
> > > /dev/YOUR_ROOT_DEV on / type ext4 (rw,noatime,data=ordered)
> > >
> > >
> > >
2507
days inactive
2508
days old
7 comments
4 participants
participants (4)
-
Arjan van de Ven -
fb.dev.clx -
Miguel Bernal Marin -
Victor Rodriguez