Hi, Wido,
> Why even try to recover the XFS filesystem?
Well, basically, our intention was to fix "D" process, and, yes, I have
to admit, at some point, to recover filesystem was kind of reflex action
while suffering storage error, it's a part of standard procedures for
traditional storage syst
On 06/02/2014 12:41 PM, Felix Lee wrote:
Hi, Craig,
Many thanks for your reply.
The disk was completely recovered, the filesystem error was caused by
fiber connection broke(cable issue), the disk/RAID itself is health, so,
there is no physical disk error but filesystem corruption in our case.
The
Hi, Craig,
Many thanks for your reply.
The disk was completely recovered, the filesystem error was caused by
fiber connection broke(cable issue), the disk/RAID itself is health, so,
there is no physical disk error but filesystem corruption in our case.
The file system itself was recovered by xfs
On 5/29/14 01:09 , Felix Lee wrote:
Dear experts,
Recently, a disk for one of our OSDs was failure and caused osd down,
after I recovered the disk and filesystem, I noticed two problems:
1. journal corruption, which causes osd failure from starting:
2. I guess I may use ceph-osd with "--mkj
Dear experts,
Recently, a disk for one of our OSDs was failure and caused osd down,
after I recovered the disk and filesystem, I noticed two problems:
1. journal corruption, which causes osd failure from starting:
-2> 2014-05-28 22:21:19.592034 7f5c6ff437a0 1 journal _open
/var/lib/ceph/
