glabel for ufs: size check is overzealous?
avg at icyb.net.ua
Wed Apr 22 13:36:36 UTC 2009
on 22/04/2009 16:12 Ivan Voras said the following:
> 2009/4/22 Andriy Gapon <avg at icyb.net.ua>:
>> on 22/04/2009 16:08 Ivan Voras said the following:
>>> 2009/4/22 Andriy Gapon <avg at icyb.net.ua>:
>>>> on 21/04/2009 21:43 Ivan Voras said the following:
>>>>> Andriy Gapon wrote:
>>>>>> I don't see why it should and - no, it actually does not.
>>>>>> fsck checks only filesystem's internal consistency, it doesn't check media size, etc.
>>>>> Well yes, if the number of blocks is really incorrect it should be
>>>>> visible from the arrangement of the metadata but still - that makes the
>>>>> field almost useless doesn't it?
>>>> How do you mean?
>>>> The field tells the filesystem size, how it can be useless?
>>> If nothing checks it and everything works, I'd say it's usefulness is
>>> a bit limited...
>> ufs driver doesn't check it, the driver *uses* it, so... :-)
> But as you said, fsck will not fix an invalid value?
It won't, because it can not know the correct value and it is probably not able to
safely derive it from anything. Filesystem size is supposed to always stay
immutable (modulo growfs), so if this type of corruption happens to superblock,
then one has quite a big problem and possibly some fun time with disk editor.
More information about the freebsd-fs