Opened 8 years ago
#13444 new enhancement
Phrase's logic of checkfs
Reported by: | Giova84 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Applications/Command Line Tools | Version: | R1/Development |
Keywords: | checkfs | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Well, I always seen this on Haiku, but since is a very minor issue (in facts i set this ticket as enhancement) I report this only now.
Ok: when I run a checkfs -c /boot
(so to perform only a check of the filesystem), if there are some blocks that could be freed, in facts, checkfs will says, for example: "5986 blocks could be freed
".
So when I run checkfs without the -c
flag (checkfs /boot
), to really fix the issues, it will say again "5986 blocks could be freed
": but these block, after such command, has been freed: is not a conditional; in facts if I run again checkfs /boot
, it will says "0 blocks could be freed
".
So, checkfs /boot
should affirm that blocks has been freed, if there are block to freed.