Date: Tue, 2 Sep 2014 10:08:08 +0800 From: Erich Dollansky <erichsfreebsdlist@alogt.com> To: Adam Vande More <amvandemore@gmail.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: du: strange behaviour Message-ID: <20140902100808.6db5c569@X220.alogt.com> In-Reply-To: <CA%2BtpaK1qsUzbhLSA=2KpftG-=ihXxtJZvR-UOzLZdFL8LadC0A@mail.gmail.com> References: <20140901235750.220be58e@X220.alogt.com> <CA%2BtpaK0uCjOS09unM25ZJMT-3wLfZKOC5wsFLzVxWx-fmui06w@mail.gmail.com> <20140902010816.49a656ee@X220.alogt.com> <CA%2BtpaK1qsUzbhLSA=2KpftG-=ihXxtJZvR-UOzLZdFL8LadC0A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Mon, 1 Sep 2014 12:41:49 -0500 Adam Vande More <amvandemore@gmail.com> wrote: > On Mon, Sep 1, 2014 at 12:08 PM, Erich Dollansky < > erichsfreebsdlist@alogt.com> wrote: > > > > > Does somebody have any ideas? > > > > > > > > > > man du | grep '\-l' > > > du -l * > > > > > I do not really get this. The other files are there but not seen > > because of hard links in /rescue? > > > > That's what the du man page says. > > > > Why is this then different on /rescue for ARM? > > > > It isn't. > > I speculate that whatever mechanism you used to populate your root > > filesystem on the arm broke the hardlinks and created many identical > > files with different names in that directory. > > > Um, that's the way it's supposed to be e.g. crunchgen(1). > I see, the problem is on the ARM side. I will have to check what went wrong there. I did not realise that /rescue contains only a single binary. Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140902100808.6db5c569>