ext3grep 前不使用umount可以么

mcsafe

根分区和数据在一起,
又不能中断服务,umount改为ro模式,
请问,可以在默认rw的方式下,使用ext3grep恢复/分区下的内容么
我好想已经扫到数据文件了,
扫描生成文件VolGroup00-LogVol00.ext3grep.stage1
里面好像有我要的东西,可以恢复时报错,请高手分析一下
#ext3grep /dev/mapper/VolGroup00-LogVol00 --ls --inode 9585140

Running ext3grep version 0.10.2
WARNING: I don't know what EXT3_FEATURE_COMPAT_EXT_ATTR is.
WARNING: EXT3_FEATURE_INCOMPAT_RECOVER is set. This either means that your partition is still mounted, and/or the file system is in an unclean state.
Number of groups: 1078
Minimum / maximum journal block: 1554 / 9756
Loading journal descriptors... sorting...Note: Block 2424 in the journal contains a copy of inode 9584645 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2424 in the journal contains a copy of inode 9584646 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2424 in the journal contains a copy of inode 9584647 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2424 in the journal contains a copy of inode 9584648 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2461 in the journal contains a copy of inode 12224741 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2461 in the journal contains a copy of inode 12224742 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2461 in the journal contains a copy of inode 12224743 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2461 in the journal contains a copy of inode 12224744 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.

WARNING: The indirect block number of inode 835744 (or a journal copy thereof) doesn't look like a block number (it is too large, block number 12 in it's block list is too large (343468382). Treating this as if one of the indirect blocks were overwritten, although this is a more serious corruption.
Note: Block 2760 in the journal contains a copy of inode 9584653 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2993 in the journal contains a copy of inode 16908325 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2993 in the journal contains a copy of inode 16908326 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2993 in the journal contains a copy of inode 16908327 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
Note: Block 2993 in the journal contains a copy of inode 16908328 which is a directory, but this directory has reused or corrupted (double/triple) indirect blocks.
done
The oldest inode block that is still in the journal, appears to be from 20108006 = Sat Aug 22 01:33:26 1970
Journal transaction 22260586 wraps around, some data blocks might have been lost of this transaction.
Number of descriptors in journal: 7970; min / max sequence numbers: 22260522 / 22260649
Inode is Allocated
Loading VolGroup00-LogVol00.ext3grep.stage1...
Result of stage one:
  27332 inodes are referenced by one or more directory blocks, 27332 of those inodes are still allocated.
  4 inodes are referenced by more than one directory block, 4 of those inodes are still allocated.
  13706 blocks contain an extended directory.
Result of stage two:
  27332 of those inodes could be resolved because they are still allocated.
All directory inodes are accounted for!

Segmentation fault