On Jun 24, 2014, at 8:46 PM, Andrey Borzenkov wrote:
> В Tue, 24 Jun 2014 11:03:06 -0600
> Chris Murphy пишет:
>
>>
>> On Jun 24, 2014, at 2:12 AM, Colin Guthrie wrote:
>>>
>>> Well, the initramfs should mount the rootfs readonly, and then it can
>>> read it's /etc/fstab (and the /forcefsck
В Tue, 24 Jun 2014 11:03:06 -0600
Chris Murphy пишет:
>
> On Jun 24, 2014, at 2:12 AM, Colin Guthrie wrote:
> >
> > Well, the initramfs should mount the rootfs readonly, and then it can
> > read it's /etc/fstab (and the /forcefsck file) and determine if any
> > further action should be taken b
On Jun 24, 2014, at 2:12 AM, Colin Guthrie wrote:
>
> Well, the initramfs should mount the rootfs readonly, and then it can
> read it's /etc/fstab (and the /forcefsck file) and determine if any
> further action should be taken before doing any kind of pivotroot type
> stuff to transition to the
'Twas brillig, and Chris Murphy at 23/06/14 23:15 did gyre and gimble:
>>> Yes this is a known problem. We should fix it, but it's not
>>> obvious to fix, since this fsck is actually run by the initrd,
>>> not the host system. There's currently no nice way to pass
>>> information about whether fsck
On Jun 23, 2014, at 5:06 PM, Mike Gilbert wrote:
> On Mon, Jun 23, 2014 at 6:15 PM, Chris Murphy wrote:
>> But in any case, is there a better way to trigger fsck for ext3/4, and not
>> for XFS and Btrfs, based on some information other than fstab fs_passno? If
>> systemd knew the root file sy
On Mon, Jun 23, 2014 at 6:15 PM, Chris Murphy wrote:
> But in any case, is there a better way to trigger fsck for ext3/4, and not
> for XFS and Btrfs, based on some information other than fstab fs_passno? If
> systemd knew the root file system type before mounting, it could always issue
> fsck
On Jun 23, 2014, at 8:42 AM, Lennart Poettering wrote:
> On Tue, 10.06.14 12:41, Chris Murphy (li...@colorremedies.com) wrote:
>
>>
>>
>> On Jun 9, 2014, at 5:24 PM, Colin Guthrie wrote:
>>
>>> 'Twas brillig, and Reindl Harald at 09/06/14 19:57 did gyre and gimble:
what disturbs me is
On Tue, 10.06.14 12:41, Chris Murphy (li...@colorremedies.com) wrote:
>
>
> On Jun 9, 2014, at 5:24 PM, Colin Guthrie wrote:
>
> > 'Twas brillig, and Reindl Harald at 09/06/14 19:57 did gyre and gimble:
> >> what disturbs me is they warning about "touch /forcefsck" while
> >> it's currently th
On Jun 9, 2014, at 5:24 PM, Colin Guthrie wrote:
> 'Twas brillig, and Reindl Harald at 09/06/14 19:57 did gyre and gimble:
>> what disturbs me is they warning about "touch /forcefsck" while
>> it's currently the *only* option to trigger a recommended fsck
>> at boot on a remote-server (and no ad
'Twas brillig, and Reindl Harald at 09/06/14 19:57 did gyre and gimble:
> what disturbs me is they warning about "touch /forcefsck" while
> it's currently the *only* option to trigger a recommended fsck
> at boot on a remote-server (and no add kernel params for that
> in the grub-config and remove
Am 09.06.2014 21:26, schrieb Alexander E. Patrakov:
> 10.06.2014 00:57, Reindl Harald wrote:
>>
>> Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
>>> 10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
> 'Twas brillig, and Reindl Harald at 08/06/1
10.06.2014 00:57, Reindl Harald wrote:
Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" leads in deprecated warnin
Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
> 10.06.2014 00:04, Reindl Harald wrote:
>>
>> Am 09.06.2014 17:05, schrieb Colin Guthrie:
>>> 'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" leads in deprecated warnings but in fact at least
10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" leads in deprecated warnings but in fact at least
on Fedora 19 *you need it* because the fsck don't happen otherwise
fo
Am 09.06.2014 17:05, schrieb Colin Guthrie:
> 'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
>> "touch /forcefsck" leads in deprecated warnings but in fact at least
>> on Fedora 19 *you need it* because the fsck don't happen otherwise
>>
>> for sure, the last reboot of the
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
> "touch /forcefsck" leads in deprecated warnings but in fact at least
> on Fedora 19 *you need it* because the fsck don't happen otherwise
>
> for sure, the last reboot of the machine below complaind too
> so why don't it hap
"touch /forcefsck" leads in deprecated warnings but in fact at least
on Fedora 19 *you need it* because the fsck don't happen otherwise
for sure, the last reboot of the machine below complaind too
so why don't it happen at boot?
Jun 8 14:51:31 localhost systemd-f
17 matches
Mail list logo
