On Tue, Apr 03, 2018 at 06:54:36AM +0000, Mik J wrote:

> Thank you Nick, I understand
> 
> I mount my partition like that
> /sbin/bioctl -s -c C -l /dev/sd0h softraid0/sbin/mount -o 
> rw,nodev,nosuid,softdep /dev/sd1c encrypted
> 
> And it appears this partition always have 0,1% of fragmentation.However the 
> mount doesn't trigger any warning when there's 0,1% fragmentation.
> >From what I understand in your answer is that I should search why I have 
> >this 0,1% fragmentation rather than something else.I don't know if this 
> >fragmentation is expected.
> Regards

You seem to be confused. fsck will print stuff about the number of
files and fragmentation etc only if was actually needed to check the
file system.  This is a line for informational purposes only, it does
not signal any problem. 

In the normal (clean) case, it will print

$ doas fsck /usr/obj   
** /dev/sd0h (6a41a900f61a2dc6.h)
** File system is clean; not checking
$

On a side note read the FAQ about creating filesystems
http://www.openbsd.org/faq/faq14.html. It is not recommended to create
a filesystem on the c (whole disk) partition.

        -Otto

>  
> 
>     Le lundi 2 avril 2018 à 14:08:45 UTC+2, Nick Holland 
> <n...@holland-consulting.net> a écrit :  
>  
>  On 04/02/18 02:28, Mik J wrote:
> 
> > @Theo: The fsck is not superfast, it takes 20s I end with that message39256 
> > files, 5904368 used, 10865841 free (15345 frags, 1356312 blocks, 0.1% 
> > fragmentation)
> 
> you missed his point.
> 
> If it took 20 seconds to run, you needed to run it.
> If you didn't need to run it, it would have said the file system was clean.
> 
> Watch:
> 
> # umount /var/www
> 
> # time doas fsck /var/www
> ** /dev/sd2p (30b584a557ce1aea.p)
> ** File system is clean; not checking
>     0m00.07s real    0m00.00s user    0m00.01s system
> 
> # doas mount -a
> 
> That's a 200G partition, btw.
> 
> I think less than a tenth of a second is quite good.  Superfast, even.
> The message you got clearly indicates that an fsck was needed.
> 
> I use this technique myself on some systems.  Just run fsck, it won't
> slow you down unless needed.
> 
> Nick.
> 
>   

Reply via email to