[PC-BSD Dev] Wild idea to speed up boot process
fabrizio at bibivu.com
Sat Aug 10 06:38:28 PDT 2013
Will open a new thread about the issue as it just happened to a
different computer... Shut it down improperly and got black screen .
Going to install the old 9.1 as people need to work but I will have a
computer that I can debug.
Sent from Fabry's iPhone
(note: all responses from this device might be addressed w/ one line
sentences and may be in shorthand format.)
On Aug 10, 2013, at 9:23, "Radio młodych bandytów"
<radiomlodychbandytow at o2.pl> wrote:
> There is no fsck for ZFS. It detects and corrects issues at runtime by
> itself. You can use scrub to force it. But if your system doesn't boot,
> it's probably damaged beyond recovery.
> zpool status?
> Twoje radio
> On 10/08/2013 14:28, Fabrizio Parrella wrote:
>> If you do it at shut down then we need to add something that checks at
>> boot if it is still valid as MANY of my users like to just press the
>> power button until the computer shuts off (lots of FSCK each day....
>> On a side note, what is the FSCK for ZFS ? I had a computer that needs
>> it with the beta version installed as it is not starting anymore)
>> Sent from Fabry's iPhone
>> (note: all responses from this device might be addressed w/ one line
>> sentences and may be in shorthand format.)
>> On Aug 10, 2013, at 5:21, Luca Ferrari <fluca1978 at infinito.it> wrote:
>>> On Fri, Aug 9, 2013 at 8:00 PM, Claudio L. <claudio at hpgcc3.org> wrote:
>>>> Once it's in RAM, any file that exists in this ram disk would be used
>>>> instead of the underlying root file system.
>>>> On system shutdown, or actually as soon as boot process is finished, this
>>>> ramdisk can be dumped back to disk, to preserve any changes.
>>>> All we would need is some hook to detect which files are read during boot,
>>>> and copy them to the ram disk on the fly if they are not already there.
>>> Uhm...sounds to me like a duplicate of the vnode cache layer: each
>>> time access to a file is detected you have to map it to the ramdisk,
>>> and then the system maps it into the vnode cache. I don't know if this
>>> will produce a real gain considering the complexity it adds.
>>> Something that could work better, in my opinion, is an autonomous
>>> system able to "adjust" a ramdisk each time the system powers off so
>>> that the next time it boots the ramdisk would be still valid
>>> considering any changes the user has done in the system itself (e.g.,
>>> configuration files).
>>> Dev mailing list
>>> Dev at lists.pcbsd.org
>> Dev mailing list
>> Dev at lists.pcbsd.org
More information about the Dev