Le 04/12/2014 17:02, Jan Ritzerfeld a écrit :

incompatible with 13.1. Reapairing it from 13.2 will destroy it:

I tried on an nearly empty data partition and xfs-repai didn't find any compatible superblock and didn't try to repair (tested with the "-n" option :-) may I use the "head" kernel fromp obs? thanks jdd NB: I considere it to be a problem to be impossible to read the next distro partition! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 04/12/2014 17:20, jdd a écrit :

Le 04/12/2014 17:13, jdd a écrit :

...

may I use the "head" kernel fromp obs?

https://en.opensuse.org/openSUSE:Kernel_of_the_day

I installed the KOTD and it boots perfectly (and read the 13.2 XFS) but I had to boot the hard way, through the grub console. Reinstalling grub2 didn't make the new kernel show in the boot menu how can I have the new kernel alongside with the old in the 13.1 grub menu? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 04/12/2014 17:24, Greg Freemyer a écrit :

I think Jan meant repairing a XFS filesystem created in 13.2 from 13.1 will destroy it.

yes, I know, but it wont (xfs-repair is smart enough). I tryed with the -n (do not execute) option, and it didn't find a suitable superblock and refused to repair.

If your filesystem contains any files of value I would absolutely post to the main xfs list. If your just testing, have at it.

I have two partition, one without importance and it's this one I tested, obviously. if it's an old kernel problem, why bother the xfs list. now I try to boot the KOTD jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-12-04 17:42, Greg Freemyer wrote:

On Thu, Dec 4, 2014 at 11:30 AM, jdd wrote:

It seems I have no idea what you are trying to accomplish. Why not just use the standard kernel with 13.2?

He wants to read on 13.1 XFS partitions created on 13.2, obviously. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSAj/AACgkQtTMYHG2NR9WkdgCgkn4P5wp97c1Dn5lQUAGCEo+g oT0An3D3SwmR6W4znXWdPbNeoalVJSvm =5Y8e -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2014-12-04 17:42, Greg Freemyer wrote:

...

On Thu, Dec 4, 2014 at 11:30 AM, jdd wrote:

...

It seems I have no idea what you are trying to accomplish. Why not just use the standard kernel with 13.2?

He wants to read on 13.1 XFS partitions created on 13.2, obviously.

Obviously? But unsupported -- "in general" (even though it might work most of the time). Sometimes the on-disk format changes. Usually, you can specify options to use the old format... inode attr={1,2} (old format for kernels older than 2.6.16) inode projecid32bit={0,1} (default changed in 3.2.0 to 'on') log version (v1 for old 2.4 kernels) log lazy-count={0,1} -- this defaults to on now, but older kernels can't process it (this might be the culprit given the timeframe). two new features that are off by default are 'crc' (metadata checksum), and a free-space inode (finobt={0,1})... both would likely create incompats with older kernels *IF* they were turned on. But it would be a bit odd for suse to turn it on given how new it is... If you can't find it, you might go for creating on 13.1 and filling on 13.2. But 'lazy-count' seems a likely culprit... good luck -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-12-04 17:02, Jan Ritzerfeld wrote:

Do not repair! The 13.1 kernel is just too old. The xfs created with 13.2 is incompatible with 13.1. Reapairing it from 13.2 will destroy it: http://lists.opensuse.org/opensuse/2014-11/msg00320.html

This issue is not mentioned in the release notes. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSAj2kACgkQtTMYHG2NR9V2pACfavbJwmsAg9txr4XPkZKReKwT ZVgAn2t804EV7px/j1qcm3xcI6g1hUX1 =UHGq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org