-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID: <alpine.LSU.2.11.1408112355480.17839@minas-tirith.valinor>
El 2014-08-11 a las 16:42 -0500, Mark Tinguely escribió:
On 08/11/14 16:31, Carlos E. R. wrote:
Does that give any ideas?
Which version of Linux?
Telcontar:~ # cat /etc/os-release
NAME=openSUSE
VERSION="13.1 (Bottle)"
VERSION_ID="13.1"
PRETTY_NAME="openSUSE 13.1 (Bottle) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
BUG_REPORT_URL="https://bugs.opensuse.org";
HOME_URL="https://opensuse.org/";
ID_LIKE="suse"
Telcontar:~ #
Telcontar:~ # uname -a
Linux Telcontar 3.11.10-17-desktop #1 SMP PREEMPT Mon Jun 16 15:28:13 UTC 2014 (fba7c1f) x86_64 x86_64 x86_64 GNU/Linux
Telcontar:~ # rpm -q xfsprogs
xfsprogs-3.2.1-40.1.x86_64
Did you get a metadata dump before the xfs_repair?
Yes, sure. I said so on another post. I'm on the process of starting up
the machine, when I noticed that error:
xfs_metadump: invalid dqblk inode number (-1)
being the first time I see that error, I'm wondering if going ahead with
mounting and using, as explained on other posts today, or wait for
different instructions from you people.
I'll try meanwhile to upload the metadata files using another machine.
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlPpPTcACgkQja8UbcUWM1wm3wD+KTezrh+/SRAFFIVGCeJcHkgE
MeJ5PMzceqDlUDOb4Q0A/jO8O5TkHCS1oDqI3zfdIExTUiel1GAcbMDNkk501Cf+
=6qE9
-----END PGP SIGNATURE-----_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
