GNU bug report logs - #26354
automake btrf inode problem

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26354 in the body.
You can then email your comments to 26354 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: aotto <aotto1968 <at> t-online.de>
To: bug-automake <at> gnu.org
Subject: automake btrf inode problem
Date: Mon, 3 Apr 2017 22:45:23 +0200

Hi… an automake build fails with the following error…

libtool: compile:  /usr/bin/ccache gcc … -MP -MF 
.deps/libmsgque_la-sqlite3.Tpo -c /XXX/libmsgque/../sqlite/sqlite3.c -o 
libmsgque_la-sqlite3.o >/dev/null 2>&1
mv -f .deps/libmsgque_la-sqlite3.Tpo .deps/libmsgque_la-sqlite3.Plo
mv: '.deps/libmsgque_la-sqlite3.Tpo' und 
'.deps/libmsgque_la-sqlite3.Plo' sind die gleiche Datei (same file)
Makefile:769: recipe for target 'libmsgque_la-sqlite3.lo' failed
make: *** [libmsgque_la-sqlite3.lo] Error 1

XXX/libmsgque> ls -i .deps/libmsgque_la-sqlite3.Tpo 
.deps/libmsgque_la-sqlite3.Plo
515890 .deps/libmsgque_la-sqlite3.Plo  515890 .deps/libmsgque_la-sqlite3.Tpo


the problem seems to me that in btrf both files share the SAME inode… !! 
515890 !!

→ mv complain about it and build fails…


what can I do… ??

Message #8 received at 26354 <at> debbugs.gnu.org (full text, mbox):

From: aotto <aotto1968 <at> t-online.de>
To: 26354 <at> debbugs.gnu.org
Subject: update on inode automake
Date: Mon, 3 Apr 2017 22:52:58 +0200

I am working in the build environment NOT on btrf…
I am working on a linux shared memory FS …
at: /dev/shm/… (every linux has this)

→ perhaps this FS has some kind of optimization to
  limit space usage.

mfg AO

Message #11 received at 26354 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Lirzin <mthl <at> gnu.org>
To: aotto <aotto1968 <at> t-online.de>
Cc: 26354 <at> debbugs.gnu.org
Subject: Re: bug#26354: update on inode automake
Date: Thu, 13 Apr 2017 16:05:18 +0200

Hello,

aotto <aotto1968 <at> t-online.de> writes:

> I am working in the build environment NOT on btrf…
> I am working on a linux shared memory FS …
> at: /dev/shm/… (every linux has this)
>
> → perhaps this FS has some kind of optimization to
>   limit space usage.
>

Could you provide a minimal way to reproduce this issue?

Thanks.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Message #16 received at 26354 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Lirzin <mthl <at> gnu.org>
To: aotto <aotto1968 <at> t-online.de>
Cc: 26354 <at> debbugs.gnu.org
Subject: Re: bug#26354: update on inode automake
Date: Sun, 16 Apr 2017 12:02:54 +0200

tags 26354 notabug
close 26354

aotto <aotto1968 <at> t-online.de> writes:

> Am 13.04.2017 um 16:05 schrieb Mathieu Lirzin:
>
>> aotto <aotto1968 <at> t-online.de> writes:
>>
>>> I am working in the build environment NOT on btrf…
>>> I am working on a linux shared memory FS …
>>> at: /dev/shm/… (every linux has this)
>>>
>>> → perhaps this FS has some kind of optimization to
>>>    limit space usage.
>>>
>> Could you provide a minimal way to reproduce this issue?
>>
>> Thanks.
>>
> I found a work around for it… I patch the PATH in the automake project
> to call MY mv command…
>> cat mv
> exec /usr/bin/mv "$@" |& grep -v "sind die gleiche Datei" && true || true
>
>
> I have a src directory on a disk and the build directory on a memory
> FS under /dev/shm/…
>
> → I think every gnu automake project with C file compiling should show
> this·bug
> →it is NOT an automake bug→I Think it is an optimization of the MEM-FS
> to save space for
> equal files…

Since This is not an Automake bug, I am closing it.

Thanks.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.