Unsure why that error does occurs when run without -f and not
when run with -f. I will need to see a o2image of the volume to
analyse.
fsck makes use of available memory. The timing depends on the
size of the volume, number of objects in the fs and available
memory.
But we do have a bug in 1.4.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sunil,
with "-fn" it runs. :-) What does the error in my last posting want to
tell me?
Unfortunately, there is no fsck. 1.4.4 for SLES 11 SP 1.
I will tell you about found errors and ask if they are repairable with
1.4.3, otherwise my colleague has
Run with -fn. It is non destructive. Also use the latest fsck. 1.4.4 I believe.
On Feb 18, 2011, at 8:46 AM, Werner Flamme wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> simple question: how can I execute a "fsck.ocfs2 /dev/sdf"?
>
> All I get is
>
> - ---snip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
simple question: how can I execute a "fsck.ocfs2 /dev/sdf"?
All I get is
- ---snip---
myhost:~ # fsck.ocfs2 /dev/sdf
fsck.ocfs2 1.4.3
Checking OCFS2 filesystem in /dev/sdf:
Label: SAP01
UUID: 5969C8CABB854
