Mailinglist Archive: opensuse-bugs (4652 mails)

< Previous Next >
[Bug 1045045] New: zypper ref fails with misleading "Cannot write file" message
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 20 Jun 2017 03:47:37 +0000
  • Message-id: <bug-1045045-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1045045


Bug ID: 1045045
Summary: zypper ref fails with misleading "Cannot write file"
message
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: 64bit
OS: SUSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: thiago@xxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

# zypper ref repo-oss
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata
-----------------------------------------------------------------[|]
Cannot write file '/var/adm/mount/AP_0xVTlAMs/content'.

Abort, retry, ignore? [a/r/i/...? shows all options] (a): r
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata
-----------------------------------------------------------------[|]
Cannot write file
'/var/adm/mount/AP_0xdHsjZc/suse/setup/descr/appdata-screenshots.tar'.

Abort, retry, ignore? [a/r/i/...? shows all options] (a):
[and so forth]

$ rpm -qi zypper
Name : zypper
Version : 1.13.28
Release : 1.1
Architecture: x86_64
Install Date: Fri Jun 9 21:07:09 2017
$ rpm -qi libzypp
Name : libzypp
Version : 16.12.0
Release : 1.1
Architecture: x86_64
Install Date: Fri Jun 9 21:06:50 2017

I have used zypper since those installations, including an "important=yes"
update according to snapper.

There is no problem with the filesystem, there's plenty of disk space left.

Inspecting the strace -f log indicates that it's having absolutely no problem
creating files in /var/adm/mount:

75898 open("/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml.new.zypp.lvF0H9",
O_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0600) = 5
75898 fcntl(5, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
75898 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2845, ...}) = 0
75898 getpid() = 75898
75898 uname({sysname="Linux", nodename="tjmaciei-mobl1", ...}) = 0
75898 write(3, "2017-06-19 20:25:30 <1> tjmaciei-mobl1(75898) [zypp++]
MediaMultiCurl.cc(doGetFileCopy):1320 dest:
/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml\n", 146) = 146
75898 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2845, ...}) = 0
75898 getpid() = 75898
75898 uname({sysname="Linux", nodename="tjmaciei-mobl1", ...}) = 0
75898 write(3, "2017-06-19 20:25:30 <1> tjmaciei-mobl1(75898) [zypp++]
MediaMultiCurl.cc(doGetFileCopy):1321 temp:
/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml.new.zypp.lvF0H9\n", 162) = 162
75898 stat("/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml", 0x7fff5cd1c3e0) =
-1 ENOENT (No such file or directory)
[later]
75898 rename("/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml.new.zypp.lvF0H9",
"/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml") = 0
75898 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2845, ...}) = 0
75898 getpid() = 75898
75898 uname({sysname="Linux", nodename="tjmaciei-mobl1", ...}) = 0
75898 write(3, "2017-06-19 20:25:30 <1> tjmaciei-mobl1(75898) [zypp]
PathInfo.cc(rename):673 rename
/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml.new.zypp.lvF0H9 ->
/var/adm/mount/AP_0xVBJWTN/repodata/repomd.xml\n", 197) = 197

There are no threads involved, otherwise I would suggest that it's a race
condition. But it's clear that it's trying to open a file before the downloaded
file is renamed to the target name.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
Follow Ups