-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thank you for your reply.
> How about showing this message in debug mode? may be under level one?
>
> Thanks,
>
The debug output is extremely verbose, even at level one (I measured hundreds
of messages per SECOND on a SATA SSD).
If we print the pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello, I know you are probably busy.
However, even though my patch is pretty bad, I'd like to know if the general
idea
of having some progress feedback interests you at all.
Perhaps it could be opt-in, using a --progress flag?
Please tell me what i
Some variable naming mistaskes were made in the last patch,
here is an updated version.
---
fsck/fsck.c | 9 +
fsck/fsck.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index ecd87af..921db0f 100644
--- a/fsck/fsck.c
+++ b/fsck/fsck.c
@@ -546,6 +546,15 @
On large SSDs filled with lots of data, fsck.f2fs can be very long to finish.
For instance, on my 1TB SSD filled at 99%, it takes literally 5 minutes to
complete.
Currently, the only way to have some feedback is to enable debug output,
but it is very verbose and doesn't tell the actual progress.
On large SSDs filled with lots of data, fsck.f2fs can be very long to finish.
For instance, on my 1TB SSD filled at 99%, it takes literally 5 minutes to
complete.
Currently, the only way to have some feedback is to enable debug output,
but it is very verbose and doesn't tell the actual progress.
