Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
* Felix Miata mrmazda@earthlink.net [05-25-14 13:52]:
Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
I do not see this on my 13.1 or Tw installs nor in vb's.
On 2014-05-25 13:54 (GMT-0400) Patrick Shanahan composed:
Felix Miata composed:
Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
I do not see this on my 13.1 or Tw installs nor in vb's.
Maybe yours are more "manual" than mine are. Mine are actually a group of noauto fstab entries I enable via script when I want them active. None of my installations are TW or virtual either. I don't routinely dup 13.1, or recall even seeing this happen in 13.1, which is why this list instead of some other. I'm guessing what's going on is systemd updates syncing /proc/mounts to fstab, oblivious to the manual post-init mount processes having taken place, but this certainly could be nfs evolutionary fallout or something else I know nothing about. IIRC this is happening in Cauldron and Rawhide as well as Factory.
On 2014-05-25 13:50 (GMT-0400) Felix Miata composed:
Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
Ping!
I asked (with more details) on linux-nfs list, and the only response there pointed to either Factory generically, or systemd: http://www.spinics.net/lists/linux-nfs/msg43660.html
On 2014-05-28 02:50, Felix Miata wrote:
On 2014-05-25 13:50 (GMT-0400) Felix Miata composed:
Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
Ping!
It happens to me on 13.1.
I have "/var/cache/zypp/packages/" shared on nfs to my server. Today I updated, with YOU, one 13.1-32bit machine, and the update crashed midway, because when nfs was umounted, the downloaded packages could not be saved.
It has happened to me more than once, and seeing your post it clicked.
This did not happen previously, on other versions.
I suppose I could have a look at my logs.
El 25/05/14 13:50, Felix Miata escribió:
Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
Since both zypp and systemd can mount and umount things..please file a bug report so who is doing what can be determined.
Since it happens when you are using zypper, it is probably a bug in libzypp.
On 2014-05-27 21:23 (GMT-0400) Cristian Rodríguez composed:
Since both zypp and systemd can mount and umount things..please file a bug report so who is doing what can be determined.
Since it happens when you are using zypper, it is probably a bug in libzypp.
https://bugzilla.novell.com/show_bug.cgi?id=880208 filed against basesystem for lack of better starting point. It seems likely to be triggered by the upgrade of nfs-client.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-05-28 04:36, Felix Miata wrote:
On 2014-05-27 21:23 (GMT-0400) Cristian Rodríguez composed:
Since both zypp and systemd can mount and umount things..please file a bug report so who is doing what can be determined.
Since it happens when you are using zypper, it is probably a bug in libzypp.
https://bugzilla.novell.com/show_bug.cgi?id=880208 filed against basesystem for lack of better starting point. It seems likely to be triggered by the upgrade of nfs-client.
I have not looked at the bug report yet, but you are right.
Look:
2014-05-27 18:15:00 <1> AmonLanc(6380) [zypp++] ExternalProgram.cc(checkStatus):503 Pid 13324 successfully completed 2014-05-27 18:15:00 <1> AmonLanc(6380) [Ruby] modules/PackageCallbacks.rb:670 Additional RPM otput: 2014-05-27 18:15:01 <1> AmonLanc(6380) [zypp] PackageProvider.cc(providePackage):212 provided Package from cache (53142)nfs-client 1.2.8-4.13.1.i586(repo-update) at /var/cache/zypp/packages/repo-update/i586/nfs-client-1.2.8-4.13.1.i586.rpm 2014-05-27 18:15:01 <1> AmonLanc(6380) [zypp] RpmDb.cc(doInstallPackage):1849 RpmDb::installPackage(/var/cache/zypp/packages/repo-update/i586/nfs-client-1.2.8-4.13.1.i586.rpm,0x0000000c) 2014-05-27 18:15:01 <1> AmonLanc(6380) [zypp++] ExternalProgram.cc(start_program):246 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--force' '--nodeps' '--' '/var/cache/zypp/packages/repo-update/i586/nfs-client-1.2.8-4.13.1.i586.rpm' 2014-05-27 18:15:01 <1> AmonLanc(6380) [zypp++] ExternalProgram.cc(start_program):402 pid 13372 launched 2014-05-27 18:15:07 <1> AmonLanc(6380) [zypp++] ExternalProgram.cc(checkStatus):503 Pid 13372 successfully completed
Then it wants to proceed with mlocate:
2014-05-27 18:15:08 <1> AmonLanc(6380) [zypp] PackageProvider.cc(providePackage):217 provide Package (52868)mlocate-0.26-4.17.1.i586(repo-update)
But fails:
2014-05-27 18:15:08 <1> AmonLanc(6380) [zypp] RepoProvideFile.cc(provideFile):252 [1]./i586/mlocate-0.26-4.13.1_4.17.1.i586.drpm{10,3 KiB|sha1-1e40fc0acc4d72b07684e74fac734aa51211a28a} 2014-05-27 18:15:08 <3> AmonLanc(6380) [zypp:fetcher] Fetcher.cc(addCachePath):330 Not adding cache '/var/cache/zypp/packages/repo-update'. Path does not exists.
2014-05-27 18:15:09 <2> AmonLanc(6380) [zypp] MediaMultiCurl.cc(run):1147 #0: state: 4 received: 10585 url: http://suse.bifi.unizar.es/opensuse/update/13.1/i586/mlocate-0.26-4.13.1_4.1...
2014-05-27 18:15:09 <2> AmonLanc(6380) [zypp] PathInfo.cc(assert_dir):353 FAILED: mkdir /var/cache/zypp/packages/repo-update/i586 00755 errno 2 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 Fetcher.cc(provideToDest):557 THROW: Can't create /var/cache/zypp/packages/repo-update/i586 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 Fetcher.cc(provideToDest):582 RETHROW: Can't create /var/cache/zypp/packages/repo-update/i586 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 History: 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 - Can't provide ./i586/mlocate-0.26-4.13.1_4.17.1.i586.drpm 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 RepoProvideFile.cc(provideFile):366 CAUGHT: Can't create /var/cache/zypp/packages/repo-update/i586 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 History: 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 - Can't provide ./i586/mlocate-0.26-4.13.1_4.17.1.i586.drpm 2014-05-27 18:15:09 <5> AmonLanc(6380) [zypp] Exception.cc(log):137 2014-05-27 18:15:09 <2> AmonLanc(6380) [zypp] RepoProvideFile.cc(provideFile):370 Trying next url
It fails because the path "/var/cache/zypp/packages/repo-update/", being nfs mounted, has disappeared in between (actually, repo-update -is a symlink to a directory mounted via nfs, precisely to make yast crash and not write the files locally instead, when the mount dissapears).
So yes, upgrade of nfs-client umounts nfs mounts. Probably it is restarted, and existing manual mounts are not remounted.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wednesday 28 May 2014, Cristian Rodríguez wrote:
El 25/05/14 13:50, Felix Miata escribió:
Is this an intentional new paradigm since several months ago, or something that will be fixed before 13.2 is released?
Since both zypp and systemd can mount and umount things..please file a bug report so who is doing what can be determined.
Since it happens when you are using zypper, it is probably a bug in libzypp.
BTW maybe libzypp could use libmount from util-linx to make things easier.
cu, Rudi
-
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Felix Miata -
Patrick Shanahan -
Ruediger Meier