Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Russ Allbery 
Andrew Deason  writes:

> But it's not, according to the 'set -x' output. There is no script
> filename passed to .../frontend. It's running this, which is why I put
> it back in the quoted context:

>> > > + exec /usr/share/debconf/frontend  configure

Oh, indeed, I missed that.  Hm.

>> I suspect the actual problem isn't so much that, now that I've looked
>> at it more, but with this bit:
>> 
>> # Only do this once.
>> if [ -z "$DEBCONF_REDIR" ]; then

> But we're not running this. If we ran that, it would appear in the 'set
> -x' output at least once, before output was redirected. (Unless
> .../frontend is re-running the script and redirecting output before it
> runs the script, but as mentioned above, I don't see how it could be
> doing that.)

Yeah, there's some piece missing here.  I've never entirely understood how
this stuff works.  I do know that set -x never works with any shell script
that uses debconf (in other words, this is not specific to OpenAFS and has
been an issue for a long time), so there's something that debconf is doing
that prevents it from working, but I don't know exactly what.

-- 
Russ Allbery (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Andrew Deason 
On Thu, 03 Oct 2013 13:15:25 -0700
Russ Allbery  wrote:

> Andrew Deason  writes:
> 
> > I'm not sure if it matters, and sorry if this is getting too far off
> > topic, but I'm not following this as the reason. It's invoking
> > /usr/share/debconf/frontend, which at least for a debian system I'm
> > glancing at, is a perl script, so of course the perl isn't going to
> > honor 'set -x'. But if you mean that that perl reinvokes the original
> > postinst shell script, I don't see how it could do so; how does it know
> > which script to run?
> 
> See /usr/share/debconf/confmodule.  Basically, it passes in $0.

But it's not, according to the 'set -x' output. There is no script
filename passed to .../frontend. It's running this, which is why I put
it back in the quoted context:

> > > + exec /usr/share/debconf/frontend  configure


> I suspect the actual problem isn't so much that, now that I've looked
> at it more, but with this bit:
> 
> # Only do this once.
> if [ -z "$DEBCONF_REDIR" ]; then

But we're not running this. If we ran that, it would appear in the 'set
-x' output at least once, before output was redirected. (Unless
.../frontend is re-running the script and redirecting output before it
runs the script, but as mentioned above, I don't see how it could be
doing that.)

-- 
Andrew Deason
adea...@sinenomine.net

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Russ Allbery 
Andrew Deason  writes:

> I'm not sure if it matters, and sorry if this is getting too far off
> topic, but I'm not following this as the reason. It's invoking
> /usr/share/debconf/frontend, which at least for a debian system I'm
> glancing at, is a perl script, so of course the perl isn't going to
> honor 'set -x'. But if you mean that that perl reinvokes the original
> postinst shell script, I don't see how it could do so; how does it know
> which script to run?

See /usr/share/debconf/confmodule.  Basically, it passes in $0.

I suspect the actual problem isn't so much that, now that I've looked at
it more, but with this bit:

# Only do this once.
if [ -z "$DEBCONF_REDIR" ]; then
# Redirect standard output to standard error. This prevents common
# mistakes by making all the output of the postinst or whatever
# script is using this library not be parsed as confmodule commands.
#
# To actually send something to standard output, send it to fd 3.
exec 3>&1
if [ "$DEBCONF_USE_CDEBCONF" ]; then
exec 1>&5
else
exec 1>&2
fi
DEBCONF_REDIR=1
export DEBCONF_REDIR
fi

I bet the -x output ends up still happening, but going off into some other
file descriptor where it gets ignored.

-- 
Russ Allbery (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Brandon Allbery 
On 10/3/13 15:47, "Andrew Deason"  wrote:

>On Thu, 03 Oct 2013 11:39:34 -0700
>Russ Allbery  wrote:
>
>> > > + exec /usr/share/debconf/frontend  configure
>[...]
>> set -x doesn't follow shell scripts through debconf because debconf does
>> some black magic to reinvoke the script.  It's one of the things that
>> makes debugging postinst scripts so "interesting."
>
>I'm not sure if it matters, and sorry if this is getting too far off
>topic, but I'm not following this as the reason. It's invoking
>/usr/share/debconf/frontend, which at least for a debian system I'm
>glancing at, is a perl script, so of course the perl isn't going to
>honor 'set -x'. But if you mean that that perl reinvokes the original
>postinst shell script, I don't see how it could do so; how does it know
>which script to run?

I suspect that's the mentioned black magic (and I can think of several
evil ways to pull it off).

-- 
brandon s allbery kf8nhsine nomine associates
allber...@gmail.com   ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad

[OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Andrew Deason 
On Thu, 03 Oct 2013 11:39:34 -0700
Russ Allbery  wrote:

> > > + exec /usr/share/debconf/frontend  configure
[...]
> set -x doesn't follow shell scripts through debconf because debconf does
> some black magic to reinvoke the script.  It's one of the things that
> makes debugging postinst scripts so "interesting."

I'm not sure if it matters, and sorry if this is getting too far off
topic, but I'm not following this as the reason. It's invoking
/usr/share/debconf/frontend, which at least for a debian system I'm
glancing at, is a perl script, so of course the perl isn't going to
honor 'set -x'. But if you mean that that perl reinvokes the original
postinst shell script, I don't see how it could do so; how does it know
which script to run?

-- 
Andrew Deason
adea...@sinenomine.net

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: [ Openafs : cache on zfs ]

2013-10-03 Thread Dale Pontius 

On 10/03/2013 02:16 PM, Andrew Deason wrote:

On Thu, 3 Oct 2013 19:34:27 +0200
nicolas prochazka  wrote:


Hello again ,
after some tests to use zfs as afs cache,
linux kernel tells :
BUG : soft lockup - CPU0 stuck for 23s ! [ afs_cachetrim:2908]

Any ideas are welcome,

It seems pretty likely from your other message that using zfsonlinux for
the openafs client cache is not going to work at all until someone takes
the time to add support for it. Just use another filesystem.

Even on other platforms, ZFS has some characteristics that make it not
ideal for a cache, and in the past I've recommended using something else
when it's easy to do so (e.g. UFS on Solaris, even if it's jus on a
zvol). At least on Solaris, ZFS does some somewhat unique things with
space allocations that have created some semi-unavoidable problems for
the cache manager.

I can understand if someone is using ZFS for their root fs, and they
don't want to make a separate fs just for the cache, but if you're
making an fs just for the cache or something, it doesn't make a lot of
sense.

My impression has always been that journalling is not only not needed 
for the afs cache, but even not desirable.  Up until recently I'd use 
the simplest thing - an ext2 partition with noatime.  On my latest 
installs I've begun using ext4 with the journal turned off, figuring 
that with any luck afs cache blocks would map to ext4 extents, giving me 
better cache performance than even ext2.  Then again somewhere else, on 
top of no journal, I got the options:


/dev/sdb6/var/cache/openafsext4 
data=writeback,barrier=0,nobh,errors=remount-ro,noatime1 2


Dale Pontius

--
Dale Pontius
Senior Engineer
IBM Corporation
Phone: (802) 769-6850
Tie-Line: 446-6850
email: pont...@us.ibm.com

This e-mail and its attachments, if any, may contain confidential and 
privileged material for the sole use of the intended recipient. Any review, 
use, distribution or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorized to receive for the recipient), please 
contact the sender by reply e-mail and delete all copies of this message from 
your system without copying it and notify sender of the misdirection by reply 
e-mail.

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Russ Allbery 
Andrew Deason  writes:

> Apparently your problem has gone away now, but here is where the error
> is coming from. I don't know if that's a bug in debconf, or if the
> openafs packaging is invoking debconf incorrectly, but that's where it's
> happening. You'd have to ask Debian (ask Russ or some other list, or
> file a bug with debconf).

set -x doesn't follow shell scripts through debconf because debconf does
some black magic to reinvoke the script.  It's one of the things that
makes debugging postinst scripts so "interesting."

-- 
Russ Allbery (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Russ Allbery 
Jean-Marc Choulet  writes:

> Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
> + [ configure = configure ]
> + update-alternatives --install /usr/bin/pagsh pagsh
> /usr/bin/pagsh.openafs 100 --slave /usr/share/man/man1/pagsh.1.gz
> pagsh.1.gz /usr/share/man/man1/pagsh.openafs.1.gz
> + update-alternatives --install /usr/bin/klog klog /usr/bin/klog.afs 10
> --slave /usr/share/man/man1/klog.1.gz klog.1.gz
> /usr/share/man/man1/klog.afs.1.gz
> + test -d /afs
> + . /usr/share/debconf/confmodule
> + [ !  ]
> + PERL_DL_NONLAZY=1
> + export PERL_DL_NONLAZY
> + [  ]
> + exec /usr/share/debconf/frontend  configure

Okay, not a problem with alternatives.  Something failed after debconf got
invoked, which unfortunately loses the set -x.  That unfortunately makes
it a lot harder to figure out what failed.

Your subsequent message indicates that there was some problem with the
local configuration that was triggering a bug in the postinst.
Unfortunately, I'm not sure what.  :/

-- 
Russ Allbery (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: [ Openafs : cache on zfs ]

2013-10-03 Thread Brandon Allbery 
On 10/3/13 14:08, "nicolas prochazka"  wrote:

>hello,
>sorry for the spam, this is a misconfigured cache option.
>Regards,
>Nicolas Prochazka.
>
>2013/10/3 nicolas prochazka :
>> Hello again ,
>> after some tests to use zfs as afs cache,
>> linux kernel tells :
>> BUG : soft lockup - CPU0 stuck for 23s ! [ afs_cachetrim:2908]

Someone should probably mention that OpenAFS cache on ZFS has performance
issues (great care is needed to get cache chunks to mesh well with ZFS
blocks and stripes; the latter are not tunable) and it's generally easier
and preferable to use a fast filesystem on a zvolume.

-- 
brandon s allbery kf8nhsine nomine associates
allber...@gmail.com   ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad

[OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Andrew Deason 
On Thu, 03 Oct 2013 18:28:09 +0200
Jean-Marc Choulet  wrote:

> + exec /usr/share/debconf/frontend  configure
> dpkg: error processing openafs-client (--configure):
>   subprocess installed post-installation script returned error exit status 1

Apparently your problem has gone away now, but here is where the error
is coming from. I don't know if that's a bug in debconf, or if the
openafs packaging is invoking debconf incorrectly, but that's where it's
happening. You'd have to ask Debian (ask Russ or some other list, or
file a bug with debconf).

-- 
Andrew Deason
adea...@sinenomine.net

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Re: [ Openafs : cache on zfs ]

2013-10-03 Thread Andrew Deason 
On Thu, 3 Oct 2013 19:34:27 +0200
nicolas prochazka  wrote:

> Hello again ,
> after some tests to use zfs as afs cache,
> linux kernel tells :
> BUG : soft lockup - CPU0 stuck for 23s ! [ afs_cachetrim:2908]
> 
> Any ideas are welcome,

It seems pretty likely from your other message that using zfsonlinux for
the openafs client cache is not going to work at all until someone takes
the time to add support for it. Just use another filesystem.

Even on other platforms, ZFS has some characteristics that make it not
ideal for a cache, and in the past I've recommended using something else
when it's easy to do so (e.g. UFS on Solaris, even if it's jus on a
zvol). At least on Solaris, ZFS does some somewhat unique things with
space allocations that have created some semi-unavoidable problems for
the cache manager.

I can understand if someone is using ZFS for their root fs, and they
don't want to make a separate fs just for the cache, but if you're
making an fs just for the cache or something, it doesn't make a lot of
sense.

-- 
Andrew Deason
adea...@sinenomine.net

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Re: [ Openafs : cache on zfs ]

2013-10-03 Thread nicolas prochazka 
hello,
sorry for the spam, this is a misconfigured cache option.
Regards,
Nicolas Prochazka.

2013/10/3 nicolas prochazka :
> Hello again ,
> after some tests to use zfs as afs cache,
> linux kernel tells :
> BUG : soft lockup - CPU0 stuck for 23s ! [ afs_cachetrim:2908]
>
> Any ideas are welcome,
> Regards,
> Nicolas Prochazka
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

We correct errors in the previous message. We solved the problem like this:

# rm -rf /etc/openafs
# apt-get remove openafs-krb5 openafs-client openafs-fileserver --purge
# apt-get -t squeeze-backports install openafs-fileserver openafs-client
# /etc/init.d/openafs-client stop
# /etc/init.d/openafs-fileserver stop
# rsync -av xxx.xxx.xxx.xxx:/etc/openafs /etc/
# /etc/init.d/openafs-client start
# /etc/init.d/openafs-fileserver start


It was not perhaps a problem with alternatives ?

Thanks,

Jean-Marc

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Le 03/10/2013 18:28, Russ Allbery a écrit :

Andrew Deason  writes:

Jean-Marc Choulet  wrote:

Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
update-alternatives: using /usr/bin/pagsh.openafs to provide
/usr/bin/pagsh (pagsh) in auto mode.
dpkg: error processing openafs-client (--configure):
   subprocess installed post-installation script returned error exit status 1

This is maybe more appropriate in a debian bug or a more debian-centric
forum, but we can try, and Russ reads this list anyway.
That doesn't seem to be telling you why the postinst script failed, and
I'm not really sure of everything that it does that can fail. But I
think you can get it to say what it's doing by doing something like this
after it fails:
Edit /var/lib/dpkg/info/openafs-client.postinst, and change the 'set -e'
near the top to 'set -xe'. Then run 'dpkg --configure --pending', or
maybe just try to install openafs-client again. It should print out a
bunch more stuff about what commands it is running, which should give a
clue as to what is actually failing. (And thanks for running with
LANG=C; that is helpful.)

This may or may not work the way that you want because of how debconf
works, but yes, that's what I'd suggest as well.

I suspect the problem is with setting up alternatives for klog, since
that's the next line immediately after setting up alternatives for pagsh.
Therefore, the output of:

 ls -l /usr/bin/klog /usr/share/man/man1/klog.1.gz \
 /etc/alternatives/klog /etc/alternatives/klog.1.gz

might be useful.  In particular, if you have an actual binary instead of a
symlink installed as /usr/bin/klog, bad things will happen (although I
would have expected some sort of error message).


Humm...

We did that :

# cp -a /etc/openafs /etc/openafs.BAK
# apt-get remove openafs-krb5 openafs-client openafs-fileserver --purge
# apt-get -t squeeze-backports install openafs-fileserver openafs-client
# /etc/init.d/openafs-client stop
# /etc/init.d/openafs-fileserver stop
# cp -a /etc/openafs.BAK/* /etc/openafs/
# /etc/init.d/openafs-client stop
# /etc/init.d/openafs-fileserver stop

Apparently, now everything works.

Jean-Marc


___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] [ Openafs : cache on zfs ]

2013-10-03 Thread nicolas prochazka 
Hello again ,
after some tests to use zfs as afs cache,
linux kernel tells :
BUG : soft lockup - CPU0 stuck for 23s ! [ afs_cachetrim:2908]

Any ideas are welcome,
Regards,
Nicolas Prochazka
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Le 03/10/2013 18:28, Russ Allbery a écrit :

ls -l /usr/bin/klog /usr/share/man/man1/klog.1.gz \
 /etc/alternatives/klog /etc/alternatives/klog.1.gz
root@fs01:~# ls -l /usr/bin/klog /usr/share/man/man1/klog.1.gz 
/etc/alternatives/klog /etc/alternatives/klog.1.gz
lrwxrwxrwx 1 root root 18  2 oct.  07:24 /etc/alternatives/klog -> 
/usr/bin/klog.krb5
lrwxrwxrwx 1 root root 34  2 oct.  07:24 /etc/alternatives/klog.1.gz -> 
/usr/share/man/man1/klog.krb5.1.gz
lrwxrwxrwx 1 root root 22  2 oct.  07:24 /usr/bin/klog -> 
/etc/alternatives/klog
lrwxrwxrwx 1 root root 27  2 oct.  07:24 /usr/share/man/man1/klog.1.gz 
-> /etc/alternatives/klog.1.gz

root@fs01:~#
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Le 03/10/2013 18:13, Andrew Deason a écrit :

On Thu, 03 Oct 2013 17:34:46 +0200
Jean-Marc Choulet  wrote:


Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
update-alternatives: using /usr/bin/pagsh.openafs to provide
/usr/bin/pagsh (pagsh) in auto mode.
dpkg: error processing openafs-client (--configure):
   subprocess installed post-installation script returned error exit status 1

This is maybe more appropriate in a debian bug or a more debian-centric
forum, but we can try, and Russ reads this list anyway.

That doesn't seem to be telling you why the postinst script failed, and
I'm not really sure of everything that it does that can fail. But I
think you can get it to say what it's doing by doing something like
this after it fails:

Edit /var/lib/dpkg/info/openafs-client.postinst, and change the 'set -e'
near the top to 'set -xe'. Then run 'dpkg --configure --pending', or
maybe just try to install openafs-client again. It should print out a
bunch more stuff about what commands it is running, which should give a
clue as to what is actually failing. (And thanks for running with
LANG=C; that is helpful.)



# vi /var/lib/dpkg/info/openafs-client.postinst
-> change set -e to set -xe

root@fs01:~# LANG=C apt-get -t squeeze-backports install 
openafs-fileserver openafs-client

Reading package lists... Done
Building dependency tree
Reading state information... Done
openafs-client is already the newest version.
openafs-fileserver is already the newest version.
The following packages were automatically installed and are no longer 
required:

  bison flex
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
+ [ configure = configure ]
+ update-alternatives --install /usr/bin/pagsh pagsh 
/usr/bin/pagsh.openafs 100 --slave /usr/share/man/man1/pagsh.1.gz 
pagsh.1.gz /usr/share/man/man1/pagsh.openafs.1.gz
+ update-alternatives --install /usr/bin/klog klog /usr/bin/klog.afs 10 
--slave /usr/share/man/man1/klog.1.gz klog.1.gz 
/usr/share/man/man1/klog.afs.1.gz

+ test -d /afs
+ . /usr/share/debconf/confmodule
+ [ !  ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [  ]
+ exec /usr/share/debconf/frontend  configure
dpkg: error processing openafs-client (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of openafs-fileserver:
 openafs-fileserver depends on openafs-client; however:
  Package openafs-client is not configured yet.
dpkg: error processing openafs-fileserver (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
  configured to not write apport 
reports

Errors were encountered while processing:
 openafs-client
 openafs-fileserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@fs01:~#
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Russ Allbery 
Andrew Deason  writes:
> Jean-Marc Choulet  wrote:

>> Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
>> update-alternatives: using /usr/bin/pagsh.openafs to provide 
>> /usr/bin/pagsh (pagsh) in auto mode.
>> dpkg: error processing openafs-client (--configure):
>>   subprocess installed post-installation script returned error exit status 1

> This is maybe more appropriate in a debian bug or a more debian-centric
> forum, but we can try, and Russ reads this list anyway.

> That doesn't seem to be telling you why the postinst script failed, and
> I'm not really sure of everything that it does that can fail. But I
> think you can get it to say what it's doing by doing something like this
> after it fails:

> Edit /var/lib/dpkg/info/openafs-client.postinst, and change the 'set -e'
> near the top to 'set -xe'. Then run 'dpkg --configure --pending', or
> maybe just try to install openafs-client again. It should print out a
> bunch more stuff about what commands it is running, which should give a
> clue as to what is actually failing. (And thanks for running with
> LANG=C; that is helpful.)

This may or may not work the way that you want because of how debconf
works, but yes, that's what I'd suggest as well.

I suspect the problem is with setting up alternatives for klog, since
that's the next line immediately after setting up alternatives for pagsh.
Therefore, the output of:

ls -l /usr/bin/klog /usr/share/man/man1/klog.1.gz \
/etc/alternatives/klog /etc/alternatives/klog.1.gz

might be useful.  In particular, if you have an actual binary instead of a
symlink installed as /usr/bin/klog, bad things will happen (although I
would have expected some sort of error message).

-- 
Russ Allbery (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Re: Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Andrew Deason 
On Thu, 03 Oct 2013 17:34:46 +0200
Jean-Marc Choulet  wrote:

> Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
> update-alternatives: using /usr/bin/pagsh.openafs to provide 
> /usr/bin/pagsh (pagsh) in auto mode.
> dpkg: error processing openafs-client (--configure):
>   subprocess installed post-installation script returned error exit status 1

This is maybe more appropriate in a debian bug or a more debian-centric
forum, but we can try, and Russ reads this list anyway.

That doesn't seem to be telling you why the postinst script failed, and
I'm not really sure of everything that it does that can fail. But I
think you can get it to say what it's doing by doing something like
this after it fails:

Edit /var/lib/dpkg/info/openafs-client.postinst, and change the 'set -e'
near the top to 'set -xe'. Then run 'dpkg --configure --pending', or
maybe just try to install openafs-client again. It should print out a
bunch more stuff about what commands it is running, which should give a
clue as to what is actually failing. (And thanks for running with
LANG=C; that is helpful.)

-- 
Andrew Deason
adea...@sinenomine.net

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Le 03/10/2013 17:35, Benjamin Kaduk a écrit :

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Le 03/10/2013 17:28, Benjamin Kaduk a écrit :

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Hello,

We want to upgrade openafs-fileserver to squeeze-backports and we 
get this errors :


LANG=C apt-get -t squeeze-backports install openafs-client


Sorry, are you upgrading the fileserver package or the client 
package? The subject and body disagree.


-Ben Kaduk
First, we made apt-get -t squeeze-backports install 
openafs-fileserver... but apt-get said it cannot install 
open-fileserver because openafs-client cannot be configured...


Did you try to install them together?
apt-get -t squeeze-backports install openafs-fileserver openafs-client 
[opeanfs-dkms] (I don't know if you're using DKMS or not).


-Ben

Yes, but we always have theses errors
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Benjamin Kaduk 

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Le 03/10/2013 17:28, Benjamin Kaduk a écrit :

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Hello,

We want to upgrade openafs-fileserver to squeeze-backports and we get this 
errors :


LANG=C apt-get -t squeeze-backports install openafs-client


Sorry, are you upgrading the fileserver package or the client package? The 
subject and body disagree.


-Ben Kaduk
First, we made apt-get -t squeeze-backports install openafs-fileserver... but 
apt-get said it cannot install open-fileserver because openafs-client cannot 
be configured...


Did you try to install them together?
apt-get -t squeeze-backports install openafs-fileserver openafs-client 
[opeanfs-dkms] (I don't know if you're using DKMS or not).


-Ben

Re: [OpenAFS] Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Le 03/10/2013 17:28, Benjamin Kaduk a écrit :

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Hello,

We want to upgrade openafs-fileserver to squeeze-backports and we get 
this errors :


LANG=C apt-get -t squeeze-backports install openafs-client


Sorry, are you upgrading the fileserver package or the client package? 
The subject and body disagree.


-Ben Kaduk



# apt-get remove openafs-client openafs-fileserver
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Le paquet openafs-client n'est pas installé, et ne peut donc être supprimé
Le paquet openafs-fileserver n'est pas installé, et ne peut donc être 
supprimé
Les paquets suivants ont été installés automatiquement et ne sont plus 
nécessaires :
  menu libmpfr4 fakeroot bison linux-kbuild-2.6.32 
linux-headers-2.6.32-5-common libgomp1 gcc-4.3 gcc-4.4 cpp libgmp3c2 gcc
  linux-headers-2.6.32-5-amd64 dkms flex openafs-modules-dkms libc6-dev 
gcc-4.3-base cpp-4.3 cpp-4.4 linux-libc-dev manpages-dev libc-dev-bin

  binutils linux-headers-2.6-amd64 make
Veuillez utiliser « apt-get autoremove » pour les supprimer.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
root@fs01:~# LANG=C apt-get -t squeeze-backports install openafs-fileserver
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

  bison flex
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  openafs-client
Suggested packages:
  openafs-doc
The following NEW packages will be installed:
  openafs-client openafs-fileserver
0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded.
Need to get 0 B/6904 kB of archives.
After this operation, 15.3 MB of additional disk space will be used.
Do you want to continue [Y/n]?
Preconfiguring packages ...
openafs-client failed to preconfigure, with exit status 1
Selecting previously deselected package openafs-client.
(Reading database ... 37939 files and directories currently installed.)
Unpacking openafs-client (from 
.../openafs-client_1.6.1-3+deb7u1~bpo60+1_amd64.deb) ...

Selecting previously deselected package openafs-fileserver.
Unpacking openafs-fileserver (from 
.../openafs-fileserver_1.6.1-3+deb7u1~bpo60+1_amd64.deb) ...

Processing triggers for man-db ...
Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
update-alternatives: using /usr/bin/pagsh.openafs to provide 
/usr/bin/pagsh (pagsh) in auto mode.

dpkg: error processing openafs-client (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of openafs-fileserver:
 openafs-fileserver depends on openafs-client; however:
  Package openafs-client is not configured yet.
dpkg: error processing openafs-fileserver (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
  configured to not write apport 
reports

Errors were encountered while processing:
 openafs-client
 openafs-fileserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@fs01:~#
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Le 03/10/2013 17:28, Benjamin Kaduk a écrit :

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Hello,

We want to upgrade openafs-fileserver to squeeze-backports and we get 
this errors :


LANG=C apt-get -t squeeze-backports install openafs-client


Sorry, are you upgrading the fileserver package or the client package? 
The subject and body disagree.


-Ben Kaduk
First, we made apt-get -t squeeze-backports install 
openafs-fileserver... but apt-get said it cannot install open-fileserver 
because openafs-client cannot be configured...





___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Benjamin Kaduk 

On Thu, 3 Oct 2013, Jean-Marc Choulet wrote:


Hello,

We want to upgrade openafs-fileserver to squeeze-backports and we get this 
errors :


LANG=C apt-get -t squeeze-backports install openafs-client


Sorry, are you upgrading the fileserver package or the client package? 
The subject and body disagree.


-Ben Kaduk
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

[OpenAFS] Update squeeze openafs-fileserver to squeeze-backports

2013-10-03 Thread Jean-Marc Choulet 

Hello,

We want to upgrade openafs-fileserver to squeeze-backports and we get 
this errors :


LANG=C apt-get -t squeeze-backports install openafs-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

  bison flex
Use 'apt-get autoremove' to remove them.
Suggested packages:
  openafs-doc
The following packages will be upgraded:
  openafs-client
1 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
1 not fully installed or removed.
Need to get 0 B/3843 kB of archives.
After this operation, 717 kB of additional disk space will be used.
Reading changelogs... Done
Preconfiguring packages ...
openafs-client failed to preconfigure, with exit status 1
(Reading database ... 38192 files and directories currently installed.)
Preparing to replace openafs-client 1.4.12.1+dfsg-4+squeeze2 (using 
.../openafs-client_1.6.1-3+deb7u1~bpo60+1_amd64.deb) ...

Unpacking replacement openafs-client ...
Processing triggers for man-db ...
Setting up openafs-client (1.6.1-3+deb7u1~bpo60+1) ...
Installing new version of config file /etc/init.d/openafs-client ...
dpkg: error processing openafs-client (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
  Errors were encountered while 
processing:

 openafs-client
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@fs01:~#

Do you any ideas ?

Thank,

Jean-Marc
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] [ OpenAFS - Cache FileSystem ]

2013-10-03 Thread Shawn McKee 
Hi Arne,

Yes, sorry for the confusion.   I missed the main word in the thread of
"cache"!

Our clients are primarily using ext4 so my comments don't really apply.

Shawn


On Thu, Oct 3, 2013 at 9:07 AM, Arne Wiebalck  wrote:

> Hi Shawn,
>
> From what I understood, you use ZFS on the servers, not the clients, right?
>
> Cheers,
>  Arne
>
>
> On Oct 3, 2013, at 3:00 PM, Shawn McKee 
>  wrote:
>
> Hi Nicolas,
>
> Just as an FYI we are running our AFS cell (atlas.umich.edu) over ZFS
>  v0.6.2 on Scientific Linux 6.4 64-bit without a problem.
>
> Shawn
>
>
> On Wed, Oct 2, 2013 at 3:48 PM, nicolas prochazka <
> prochazka.nico...@gmail.com> wrote:
>
>> Hello,
>> For your intention,
>> In Faq, we can read :
>>
>> The OpenAFS cache manager will detect an unsupported filesystem and
>> refuse to start.
>>
>> The following file systems have been reported to work for the AFS client
>> cache:
>>
>> ext2
>> ext3
>> hfs (HP-UX)
>> xfs (at least on IRIX 6.5)
>> ufs (Solaris, ?Tru64Unix)
>>
>>
>> But if I configure cache on zfs on linux ( zfsonlinux.org) ,
>> i got kernel panic :
>>
>> [114328.841466] Starting AFS cache scan...
>> [114349.618208] openafs: Inconsistent file handles within cache
>> [114349.618238] [ cut here ]
>> [114349.618926] kernel BUG at
>> /tmp/openafs/src/libafs/MODLOAD-3.11.2-MP/osi_file.c:129!
>> [114349.620004] invalid opcode:  [#1] SMP
>> [114349.620004] Modules linked in: libafs(PO) zfs(PO) zunicode(PO)
>> zavl(PO) zcommon(PO) znvpair(PO) spl(O) kvm_intel kvm
>> [114349.620004] CPU: 0 PID: 32590 Comm: afsd Tainted: P   O
>> 3.11.2 #1
>> [114349.620004] Hardware name: NEC Express5800/120Rj-2
>> [N8100-1407E]/MS-9192-01S, BIOS 1.0.4S31 03/05/2010
>> [114349.620004] task: 88076e5f2000 ti: 880559c6c000 task.ti:
>> 880559c6c000
>> [114349.620004] RIP: 0010:[]  []
>> osi_get_fh+0xc8/0xe0 [libafs]
>> [114349.620004] RSP: 0018:880559c6dc38  EFLAGS: 00010296
>> [114349.620004] RAX: 002f RBX: 0007 RCX:
>> 
>> [114349.620004] RDX: 88082fc0fa88 RSI: 88082fc0e178 RDI:
>> 0246
>> [114349.620004] RBP: 880559c6dc48 R08: 0400 R09:
>> 82716488
>> [114349.635745] R10: 041c R11: 041b R12:
>> 
>> [114349.635745] R13: 0062dd80 R14: 88077ad03800 R15:
>> 0001
>> [114349.635745] FS:  7f2afb49c700() GS:88082fc0()
>> knlGS:
>> [114349.635745] CS:  0010 DS:  ES:  CR0: 80050033
>> [114349.635745] CR2: 7398600c CR3: 0005583ef000 CR4:
>> 27e0
>> [114349.635745] Stack:
>> [114349.635745]  88077ad03800 00030001 880559c6dc68
>> a02975c0
>> [114349.635745]  880559c6dc88 88051fdb6900 880559c6dca8
>> a025ddfa
>> [114349.635745]  880559c6dc98 81064565 880559c6dca8
>> 81f182cd
>> [114349.635745] Call Trace:
>> [114349.635745]  [] osi_InitCacheInfo+0x40/0x80 [libafs]
>> [114349.635745]  [] afs_InitCacheInfo+0x2a/0x130
>> [libafs]
>> [114349.635745]  [] ? ns_capable+0x35/0x60
>> [114349.635745]  [] ? mutex_lock+0x1d/0x50
>> [114349.635745]  [] afs_syscall_call+0x105e/0x1bf0
>> [libafs]
>> [114349.635745]  [] ? do_last.isra.57+0x11b/0xc60
>> [114349.635745]  [] ? inode_permission+0x18/0x50
>> [114349.635745]  [] ? link_path_walk+0x23d/0x8e0
>> [114349.635745]  [] ? lg_local_unlock+0x1a/0x20
>> [114349.635745]  [] ? mntput_no_expire+0x49/0x160
>> [114349.635745]  [] afs_syscall+0x17c/0x650 [libafs]
>> [114349.635745]  [] afs_unlocked_ioctl+0x69/0xd0
>> [libafs]
>> [114349.635745]  [] proc_reg_unlocked_ioctl+0x3f/0x70
>> [114349.635745]  [] do_vfs_ioctl+0x8b/0x4f0
>> [114349.635745]  [] ? final_putname+0x26/0x50
>> [114349.635745]  [] SyS_ioctl+0x50/0x90
>> [114349.635745]  [] system_call_fastpath+0x16/0x1b
>> [114349.635745] Code: 8b 0d 75 2c 02 00 89 05 73 2c 02 00 89 c2 85 c9
>> 79 ac 8b 4d fc 89 0d 60 2c 02 00 eb a1 48 c7 c7 08 42 2b a0 31 c0 e8
>> 3a 40 c7 e1 <0f> 0b 48 c7 c7 e0 41 2b a0 31 c0 e8 2a 40 c7 e1 0f 0b 66
>> 0f 1f
>> [114349.635745] RIP  [] osi_get_fh+0xc8/0xe0 [libafs]
>> [114349.635745]  RSP 
>> [114351.110672] ---[ end trace b1f29ac8defa1347 ]---
>> ___
>> OpenAFS-info mailing list
>> OpenAFS-info@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-info
>>
>
>
>

Re: [OpenAFS] [ OpenAFS - Cache FileSystem ]

2013-10-03 Thread Arne Wiebalck 
Hi Shawn,

From what I understood, you use ZFS on the servers, not the clients, right?

Cheers,
 Arne


On Oct 3, 2013, at 3:00 PM, Shawn McKee 
 wrote:

> Hi Nicolas,
> 
> Just as an FYI we are running our AFS cell (atlas.umich.edu) over ZFS  v0.6.2 
> on Scientific Linux 6.4 64-bit without a problem.
> 
> Shawn
> 
> 
> On Wed, Oct 2, 2013 at 3:48 PM, nicolas prochazka 
>  wrote:
> Hello,
> For your intention,
> In Faq, we can read :
> 
> The OpenAFS cache manager will detect an unsupported filesystem and
> refuse to start.
> 
> The following file systems have been reported to work for the AFS client 
> cache:
> 
> ext2
> ext3
> hfs (HP-UX)
> xfs (at least on IRIX 6.5)
> ufs (Solaris, ?Tru64Unix)
> 
> 
> But if I configure cache on zfs on linux ( zfsonlinux.org) ,
> i got kernel panic :
> 
> [114328.841466] Starting AFS cache scan...
> [114349.618208] openafs: Inconsistent file handles within cache
> [114349.618238] [ cut here ]
> [114349.618926] kernel BUG at
> /tmp/openafs/src/libafs/MODLOAD-3.11.2-MP/osi_file.c:129!
> [114349.620004] invalid opcode:  [#1] SMP
> [114349.620004] Modules linked in: libafs(PO) zfs(PO) zunicode(PO)
> zavl(PO) zcommon(PO) znvpair(PO) spl(O) kvm_intel kvm
> [114349.620004] CPU: 0 PID: 32590 Comm: afsd Tainted: P   O 3.11.2 #1
> [114349.620004] Hardware name: NEC Express5800/120Rj-2
> [N8100-1407E]/MS-9192-01S, BIOS 1.0.4S31 03/05/2010
> [114349.620004] task: 88076e5f2000 ti: 880559c6c000 task.ti:
> 880559c6c000
> [114349.620004] RIP: 0010:[]  []
> osi_get_fh+0xc8/0xe0 [libafs]
> [114349.620004] RSP: 0018:880559c6dc38  EFLAGS: 00010296
> [114349.620004] RAX: 002f RBX: 0007 RCX:
> 
> [114349.620004] RDX: 88082fc0fa88 RSI: 88082fc0e178 RDI:
> 0246
> [114349.620004] RBP: 880559c6dc48 R08: 0400 R09:
> 82716488
> [114349.635745] R10: 041c R11: 041b R12:
> 
> [114349.635745] R13: 0062dd80 R14: 88077ad03800 R15:
> 0001
> [114349.635745] FS:  7f2afb49c700() GS:88082fc0()
> knlGS:
> [114349.635745] CS:  0010 DS:  ES:  CR0: 80050033
> [114349.635745] CR2: 7398600c CR3: 0005583ef000 CR4:
> 27e0
> [114349.635745] Stack:
> [114349.635745]  88077ad03800 00030001 880559c6dc68
> a02975c0
> [114349.635745]  880559c6dc88 88051fdb6900 880559c6dca8
> a025ddfa
> [114349.635745]  880559c6dc98 81064565 880559c6dca8
> 81f182cd
> [114349.635745] Call Trace:
> [114349.635745]  [] osi_InitCacheInfo+0x40/0x80 [libafs]
> [114349.635745]  [] afs_InitCacheInfo+0x2a/0x130 [libafs]
> [114349.635745]  [] ? ns_capable+0x35/0x60
> [114349.635745]  [] ? mutex_lock+0x1d/0x50
> [114349.635745]  [] afs_syscall_call+0x105e/0x1bf0 [libafs]
> [114349.635745]  [] ? do_last.isra.57+0x11b/0xc60
> [114349.635745]  [] ? inode_permission+0x18/0x50
> [114349.635745]  [] ? link_path_walk+0x23d/0x8e0
> [114349.635745]  [] ? lg_local_unlock+0x1a/0x20
> [114349.635745]  [] ? mntput_no_expire+0x49/0x160
> [114349.635745]  [] afs_syscall+0x17c/0x650 [libafs]
> [114349.635745]  [] afs_unlocked_ioctl+0x69/0xd0 [libafs]
> [114349.635745]  [] proc_reg_unlocked_ioctl+0x3f/0x70
> [114349.635745]  [] do_vfs_ioctl+0x8b/0x4f0
> [114349.635745]  [] ? final_putname+0x26/0x50
> [114349.635745]  [] SyS_ioctl+0x50/0x90
> [114349.635745]  [] system_call_fastpath+0x16/0x1b
> [114349.635745] Code: 8b 0d 75 2c 02 00 89 05 73 2c 02 00 89 c2 85 c9
> 79 ac 8b 4d fc 89 0d 60 2c 02 00 eb a1 48 c7 c7 08 42 2b a0 31 c0 e8
> 3a 40 c7 e1 <0f> 0b 48 c7 c7 e0 41 2b a0 31 c0 e8 2a 40 c7 e1 0f 0b 66
> 0f 1f
> [114349.635745] RIP  [] osi_get_fh+0xc8/0xe0 [libafs]
> [114349.635745]  RSP 
> [114351.110672] ---[ end trace b1f29ac8defa1347 ]---
> ___
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [OpenAFS] [ OpenAFS - Cache FileSystem ]

2013-10-03 Thread Shawn McKee 
Hi Nicolas,

Just as an FYI we are running our AFS cell (atlas.umich.edu) over ZFS
 v0.6.2 on Scientific Linux 6.4 64-bit without a problem.

Shawn


On Wed, Oct 2, 2013 at 3:48 PM, nicolas prochazka <
prochazka.nico...@gmail.com> wrote:

> Hello,
> For your intention,
> In Faq, we can read :
>
> The OpenAFS cache manager will detect an unsupported filesystem and
> refuse to start.
>
> The following file systems have been reported to work for the AFS client
> cache:
>
> ext2
> ext3
> hfs (HP-UX)
> xfs (at least on IRIX 6.5)
> ufs (Solaris, ?Tru64Unix)
>
>
> But if I configure cache on zfs on linux ( zfsonlinux.org) ,
> i got kernel panic :
>
> [114328.841466] Starting AFS cache scan...
> [114349.618208] openafs: Inconsistent file handles within cache
> [114349.618238] [ cut here ]
> [114349.618926] kernel BUG at
> /tmp/openafs/src/libafs/MODLOAD-3.11.2-MP/osi_file.c:129!
> [114349.620004] invalid opcode:  [#1] SMP
> [114349.620004] Modules linked in: libafs(PO) zfs(PO) zunicode(PO)
> zavl(PO) zcommon(PO) znvpair(PO) spl(O) kvm_intel kvm
> [114349.620004] CPU: 0 PID: 32590 Comm: afsd Tainted: P   O
> 3.11.2 #1
> [114349.620004] Hardware name: NEC Express5800/120Rj-2
> [N8100-1407E]/MS-9192-01S, BIOS 1.0.4S31 03/05/2010
> [114349.620004] task: 88076e5f2000 ti: 880559c6c000 task.ti:
> 880559c6c000
> [114349.620004] RIP: 0010:[]  []
> osi_get_fh+0xc8/0xe0 [libafs]
> [114349.620004] RSP: 0018:880559c6dc38  EFLAGS: 00010296
> [114349.620004] RAX: 002f RBX: 0007 RCX:
> 
> [114349.620004] RDX: 88082fc0fa88 RSI: 88082fc0e178 RDI:
> 0246
> [114349.620004] RBP: 880559c6dc48 R08: 0400 R09:
> 82716488
> [114349.635745] R10: 041c R11: 041b R12:
> 
> [114349.635745] R13: 0062dd80 R14: 88077ad03800 R15:
> 0001
> [114349.635745] FS:  7f2afb49c700() GS:88082fc0()
> knlGS:
> [114349.635745] CS:  0010 DS:  ES:  CR0: 80050033
> [114349.635745] CR2: 7398600c CR3: 0005583ef000 CR4:
> 27e0
> [114349.635745] Stack:
> [114349.635745]  88077ad03800 00030001 880559c6dc68
> a02975c0
> [114349.635745]  880559c6dc88 88051fdb6900 880559c6dca8
> a025ddfa
> [114349.635745]  880559c6dc98 81064565 880559c6dca8
> 81f182cd
> [114349.635745] Call Trace:
> [114349.635745]  [] osi_InitCacheInfo+0x40/0x80 [libafs]
> [114349.635745]  [] afs_InitCacheInfo+0x2a/0x130 [libafs]
> [114349.635745]  [] ? ns_capable+0x35/0x60
> [114349.635745]  [] ? mutex_lock+0x1d/0x50
> [114349.635745]  [] afs_syscall_call+0x105e/0x1bf0
> [libafs]
> [114349.635745]  [] ? do_last.isra.57+0x11b/0xc60
> [114349.635745]  [] ? inode_permission+0x18/0x50
> [114349.635745]  [] ? link_path_walk+0x23d/0x8e0
> [114349.635745]  [] ? lg_local_unlock+0x1a/0x20
> [114349.635745]  [] ? mntput_no_expire+0x49/0x160
> [114349.635745]  [] afs_syscall+0x17c/0x650 [libafs]
> [114349.635745]  [] afs_unlocked_ioctl+0x69/0xd0 [libafs]
> [114349.635745]  [] proc_reg_unlocked_ioctl+0x3f/0x70
> [114349.635745]  [] do_vfs_ioctl+0x8b/0x4f0
> [114349.635745]  [] ? final_putname+0x26/0x50
> [114349.635745]  [] SyS_ioctl+0x50/0x90
> [114349.635745]  [] system_call_fastpath+0x16/0x1b
> [114349.635745] Code: 8b 0d 75 2c 02 00 89 05 73 2c 02 00 89 c2 85 c9
> 79 ac 8b 4d fc 89 0d 60 2c 02 00 eb a1 48 c7 c7 08 42 2b a0 31 c0 e8
> 3a 40 c7 e1 <0f> 0b 48 c7 c7 e0 41 2b a0 31 c0 e8 2a 40 c7 e1 0f 0b 66
> 0f 1f
> [114349.635745] RIP  [] osi_get_fh+0xc8/0xe0 [libafs]
> [114349.635745]  RSP 
> [114351.110672] ---[ end trace b1f29ac8defa1347 ]---
> ___
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>

Re: [OpenAFS] [ OpenAFS - Cache FileSystem ]

2013-10-03 Thread nicolas prochazka 
Ok,
thanks for this precision about openafs cache.
Regards,
Nicolas Prochazka

2013/10/3 Marc Dionne :
> On Wed, Oct 2, 2013 at 3:48 PM, nicolas prochazka
>  wrote:
>> Hello,
>> For your intention,
>> In Faq, we can read :
>>
>> The OpenAFS cache manager will detect an unsupported filesystem and
>> refuse to start.
>>
>> The following file systems have been reported to work for the AFS client 
>> cache:
>>
>> ext2
>> ext3
>> hfs (HP-UX)
>> xfs (at least on IRIX 6.5)
>> ufs (Solaris, ?Tru64Unix)
>
> That information is somewhat outdated; for more recent OpenAFS
> releases and Linux kernels there are no runtime checks, and any
> filesystem that is exportable by NFS has a good chance of being usable
> for holding the client cache.  So the list of possible filesystems is
> substantially larger than the above.
>
>> But if I configure cache on zfs on linux ( zfsonlinux.org) ,
>> i got kernel panic :
>>
>> [114328.841466] Starting AFS cache scan...
>> [114349.618208] openafs: Inconsistent file handles within cache
>
> I haven't looked at zfs code closely, but that message suggests that
> - zfs does provide the necessary exportfs API calls, so should be
> usable in theory
> - maybe your cache location crosses a mount point between zfs and some
> other filesystem
> - or, zfs produces file handles of variable length.  The current
> client code assumes that handles have a constant size, so if this is
> the case, some changes will be required before zfs can be used to hold
> the AFS disk cache.
>
> Marc
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info