From: Marko Weber|8000 <weber@zbfmail.de>
To: Xfs <xfs@oss.sgi.com>
Subject: xfs_db dont work on blocksize 4096?
Date: Wed, 14 May 2014 14:47:16 +0200 [thread overview]
Message-ID: <e6b0d925a9409122a92d4e14922a26fd@zbfmail.de> (raw)
hello,
does xfs_db not work on blocksize 4096 ?
i get this:
bunka distfiles # xfs_db -r /dev/sda4
xfs_db: error - read only 0 of 512 bytes
cache_node_purge: refcount was 1, not zero (node=0x686530)
xfs_db: cannot read root inode (117)
cache_node_purge: refcount was 1, not zero (node=0x688810)
xfs_db: cannot read realtime bitmap inode (117)
xfs_db: error - read only 0 of 512 bytes
xfs_db> quit
any hints, ideas tipps?
thank you
marko
--
zbfmail - Mittendrin statt nur Datei!
OpenDKIM, SPF, DSPAM, Greylisting, POSTSCREEN, AMAVIS, Mailgateways
Mailfiltering, SMTP Service, Spam Abwehr, MX-Backup, Mailserver Backup
Redundante Mailgateways, HA Mailserver, Secure Mailserver
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-05-14 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 12:47 Marko Weber|8000 [this message]
2014-05-14 14:06 ` xfs_db dont work on blocksize 4096? Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6b0d925a9409122a92d4e14922a26fd@zbfmail.de \
--to=weber@zbfmail.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox