xfs_fsr broken again?

[Juha K Kallio]

I'm running a 2 days old CVS kernel, and 2 days old xfsprogs. The new
xfs_fsr worked OK, before I upgraded the kernel too. After that, it just
produces *lots* of lines like this:
could not pre-alloc tmp space: /.fsr/ag1/tmp427
could not pre-alloc tmp space: /.fsr/ag2/tmp427
could not pre-alloc tmp space: /.fsr/ag3/tmp427

I've included the strace output as an attachment.

[Juha K Kallio]

I am running it as root, and setuid bit is not set. Running as non-root
comes with this: could not create tmpdir: //.fsr: Permission denied.
BTW, what's that double slash there?

***@jaenoe:~ > /usr/sbin/xfs_fsr -V
xfs_fsr version 2.2.0
***@jaenoe:~ > dmesg|grep ^SGI\ XFS
SGI XFS CVS-10/07/02:05 with no debug enabled

[Juha K Kallio]

And here's the strace, sine I forgot that in the last post ;)

[Nathan Scott]

Post by Juha K Kallio
I'm running a 2 days old CVS kernel, and 2 days old xfsprogs. The new
xfs_fsr worked OK, before I upgraded the kernel too. After that, it just
could not pre-alloc tmp space: /.fsr/ag1/tmp427
could not pre-alloc tmp space: /.fsr/ag2/tmp427
could not pre-alloc tmp space: /.fsr/ag3/tmp427

Do you have free space on the filesystem (df)? xfs_fsr has to
preallocate space for the new, improved file layout to occupy,
so if you're out of space these errors kinda make sense...

cheers.

[Juha K Kallio]

Sorry, I just noticed that xfs_fsr was in xfsdump, not in xfsprogs. So
that should be it. But I ran into another problem when updating
everything: I made a Debian package of attr with debuild, and it made a
very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
missing from /usr/lib.

[Christian Guggenberger]

Post by Juha K Kallio
Sorry, I just noticed that xfs_fsr was in xfsdump, not in xfsprogs. So
that should be it. But I ran into another problem when updating
everything: I made a Debian package of attr with debuild, and it made a
very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
missing from /usr/lib.

Hi,

I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should check
again?!
But I can build proper packages on a debian woody system....

But you can use the latest xfsprogs, xfsdump and attr binary packages from
debian/unstable, they contain the fixes Eric checked in last week.

Christian

[Ethan Benson]

Post by Christian Guggenberger

Post by Juha K Kallio
Sorry, I just noticed that xfs_fsr was in xfsdump, not in xfsprogs. So
that should be it. But I ran into another problem when updating
everything: I made a Debian package of attr with debuild, and it made a
very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
missing from /usr/lib.

Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should check
again?!
But I can build proper packages on a debian woody system....
But you can use the latest xfsprogs, xfsdump and attr binary packages from
debian/unstable, they contain the fixes Eric checked in last week.

what does /bin/sh point to on your box? this smells like evil
bashisms in the xfsprogs build system, this would not show up on boxes
using BloAtedSH as /bin/sh but would on boxes using a more purly posix
shell such as debian's ash.

[Juha K Kallio]

Post by Ethan Benson

Post by Christian Guggenberger

Post by Juha K Kallio
Sorry, I just noticed that xfs_fsr was in xfsdump, not in xfsprogs. So
that should be it. But I ran into another problem when updating
everything: I made a Debian package of attr with debuild, and it made a
very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
missing from /usr/lib.

Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should check
again?!
But I can build proper packages on a debian woody system....
But you can use the latest xfsprogs, xfsdump and attr binary packages from
debian/unstable, they contain the fixes Eric checked in last week.

what does /bin/sh point to on your box? this smells like evil
bashisms in the xfsprogs build system, this would not show up on boxes
using BloAtedSH as /bin/sh but would on boxes using a more purly posix
shell such as debian's ash.
--
Ethan Benson
http://www.alaska.net/~erbenson/

It points to bash, and the system is quite "debianish", no manual
hackings done. Yes, I'm using unstable

[Christian Guggenberger]

Post by Juha K Kallio

Post by Ethan Benson

Post by Christian Guggenberger

Post by Juha K Kallio
Sorry, I just noticed that xfs_fsr was in xfsdump, not in xfsprogs.

So

Post by Ethan Benson

Post by Christian Guggenberger

Post by Juha K Kallio
that should be it. But I ran into another problem when updating
everything: I made a Debian package of attr with debuild, and it

made a

Post by Ethan Benson

Post by Christian Guggenberger

Post by Juha K Kallio
very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
missing from /usr/lib.

Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should

check

Post by Ethan Benson

Post by Christian Guggenberger
again?!
But I can build proper packages on a debian woody system....
But you can use the latest xfsprogs, xfsdump and attr binary packages

from

Post by Ethan Benson

Post by Christian Guggenberger
debian/unstable, they contain the fixes Eric checked in last week.

what does /bin/sh point to on your box? this smells like evil
bashisms in the xfsprogs build system, this would not show up on boxes
using BloAtedSH as /bin/sh but would on boxes using a more purly posix
shell such as debian's ash.
--
Ethan Benson
http://www.alaska.net/~erbenson/

It points to bash, and the system is quite "debianish", no manual
hackings done. Yes, I'm using unstable

same here on my unstable box...

[Nathan Scott]

Post by Christian Guggenberger
Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should check
again?!
...
But you can use the latest xfsprogs, xfsdump and attr binary packages from
debian/unstable, they contain the fixes Eric checked in last week.

*cough* -- those would be the packages I built on my (debian/unstable)
laptop just yesterday, right? ;-)

cheers.

[Christian Guggenberger]

Post by Nathan Scott

Post by Christian Guggenberger
Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should

check

Post by Christian Guggenberger
again?!
...
But you can use the latest xfsprogs, xfsdump and attr binary packages

from

Post by Christian Guggenberger
debian/unstable, they contain the fixes Eric checked in last week.

*cough* -- those would be the packages I built on my (debian/unstable)
laptop just yesterday, right? ;-)

It seems to be a problem, when building those debian packages on a
xfs-Partition... the Problem seems to be in tar... I get proper builds on
an ext3 filesystem...

This is what I get on my /usr xfs filesystem:

bonnie79:/usr/local/src/attr-2.0.12/debian# tar czvf attr.tgz attr-dev
attr-dev/
attr-dev/usr/
attr-dev/usr/include/
attr-dev/usr/include/attr/
attr-dev/usr/include/attr/attributes.h
attr-dev/usr/include/attr/xattr.h
attr-dev/usr/lib/
attr-dev/usr/lib/libattr.a
attr-dev/usr/lib/libattr.la
attr-dev/usr/lib/libattr.so
attr-dev/usr/share/
attr-dev/usr/share/man/
attr-dev/usr/share/man/man2/
attr-dev/usr/share/man/man2/getxattr.2.gz
attr-dev/usr/share/man/man2/listxattr.2.gz
attr-dev/usr/share/man/man2/removexattr.2.gz
attr-dev/usr/share/man/man2/setxattr.2.gz
attr-dev/usr/share/man/man2/lgetxattr.2.gz
attr-dev/usr/share/man/man2/fgetxattr.2.gz
attr-dev/usr/share/man/man2/llistxattr.2.gz
attr-dev/usr/share/man/man2/flistxattr.2.gz
attr-dev/usr/share/man/man2/lremovexattr.2.gz
attr-dev/usr/share/man/man2/fremovexattr.2.gz
attr-dev/usr/share/man/man2/lsetxattr.2.gz
attr-dev/usr/share/man/man2/fsetxattr.2.gz
attr-dev/usr/share/man/man3/
attr-dev/usr/share/man/man3/attr_get.3.gz
attr-dev/usr/share/man/man3/attr_multi.3.gz
attr-dev/usr/share/man/man3/attr_remove.3.gz
attr-dev/usr/share/man/man3/attr_set.3.gz
attr-dev/usr/share/man/man3/attr_getf.3.gz
attr-dev/usr/share/man/man3/attr_multif.3.gz
attr-dev/usr/share/man/man3/attr_removef.3.gz
attr-dev/usr/share/man/man3/attr_setf.3.gz
attr-dev/usr/share/doc/
attr-dev/usr/share/doc/attr/
attr-dev/usr/share/doc/attr-dev/
attr-dev/usr/share/doc/attr-dev/copyright
attr-dev/usr/share/doc/attr-dev/changelog.Debian.gz
attr-dev/lib/
attr-dev/lib/libattr.so
attr-dev/lib/libattr.a
attr-dev/lib/libattr.la
attr-dev/DEBIAN/
attr-dev/DEBIAN/control
attr-dev/DEBIAN/md5sums

the tar-archive is attached.
tar version:

bonnie79:/usr/local/src/attr-2.0.12/debian# dpkg -l tar
ii tar 1.13.25-3 GNU tar


Christian

[Christian Guggenberger]

Post by Christian Guggenberger

Post by Nathan Scott

Post by Christian Guggenberger
Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should

check

Post by Christian Guggenberger
again?!
...
But you can use the latest xfsprogs, xfsdump and attr binary packages

from

Post by Christian Guggenberger
debian/unstable, they contain the fixes Eric checked in last week.

*cough* -- those would be the packages I built on my (debian/unstable)
laptop just yesterday, right? ;-)

It seems to be a problem, when building those debian packages on a
xfs-Partition... the Problem seems to be in tar... I get proper builds
on an ext3 filesystem...

....

i just checked again on a system running CVS Kernel of September, 2nd;
this machine has no Problems with "false" symlink names in a tarred
archive. My previous tests (which showed those symlink problems in tar
archives) had been run on today's CVS Kernel ...

Christian

[Steve Lord]

Post by Christian Guggenberger

Post by Christian Guggenberger

Post by Nathan Scott

Post by Christian Guggenberger
Hi,
I have the same problems here on my debian/unstable box. According to
Nathan Scott the builds are fine on his box... maybe Nathan should

check

Post by Christian Guggenberger
again?!
...
But you can use the latest xfsprogs, xfsdump and attr binary packages

from

Post by Christian Guggenberger
debian/unstable, they contain the fixes Eric checked in last week.

*cough* -- those would be the packages I built on my (debian/unstable)
laptop just yesterday, right? ;-)

It seems to be a problem, when building those debian packages on a
xfs-Partition... the Problem seems to be in tar... I get proper builds
on an ext3 filesystem...

....
i just checked again on a system running CVS Kernel of September, 2nd;
this machine has no Problems with "false" symlink names in a tarred
archive. My previous tests (which showed those symlink problems in tar
archives) had been run on today's CVS Kernel ...
Christian

The length of a symlink appears to be getting messed up. I will take a
look since I made some changes in this area recently.

Steve

[Nathan Scott]

... that should be it. But I ran into another problem when updating
everything: I made a Debian package of attr with debuild, and it made a
very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
missing from /usr/lib.

Hmmm... you're the second person to report that. No idea why that
happens, it works fine for me (TM). Maybe you can investigate and
get back to me with some build logs, configure files, etc, & maybe
even an explanation.

thanks.