Package: ocfs2-tools
Version: 1.6.4-2
Severity: normal

Dear Maintainer,

I had for quite some time a corrupted ocfs2 for which fsck.ocfs2 failed
to fix it with exit status 8 and output like:
Pass 0a: Checking cluster allocation chains
Pass 0b: Checking inode allocation chains
Pass 0c: Checking extent block allocation chains
Pass 1: Checking inodes and blocks
Duplicate clusters detected.  Pass 1b will be run
Running additional passes to resolve clusters claimed by more than one inode...
Pass 1b: Determining ownership of multiply-claimed clusters
pass1b: Inode type does not contain extents while processing inode 5
fsck.ocfs2: Inode type does not contain extents while performing pass 1

Finally I got it fixed using current debian/unstable version (1.6.4-2) +
cherry picking commit 45133dc9883b4020c96154660b550563fdb8d529 from
upstream git (git://oss.oracle.com/git/ocfs2-tools.git).

greetings,
karme

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ocfs2-tools depends on:
ii  debconf [debconf-2.0]  1.5.46
ii  libc6                  2.13-35
ii  libcomerr2             1.42.5-1
ii  libglib2.0-0           2.33.12+really2.32.4-3
ii  libncurses5            5.9-10
ii  libreadline6           6.2-8
ii  libtinfo5              5.9-10
ii  libuuid1               2.20.1-5.2
ii  psmisc                 22.19-1

ocfs2-tools recommends no packages.

Versions of packages ocfs2-tools suggests:
pn  ocfs2-tools-cman       <none>
pn  ocfs2-tools-pacemaker  <none>
pn  ocfs2console           <none>

-- debconf information:
* ocfs2-tools/heartbeat_threshold: 31
* ocfs2-tools/reconnect_delay: 2000
* ocfs2-tools/init: true
* ocfs2-tools/keepalive_delay: 2000
* ocfs2-tools/clustername: ocfs2
* ocfs2-tools/idle_timeout: 30000


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to