From: Michael Brunnbauer <brunni@netestate.de>
To: Jan Kara <jack@suse.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
jeffm@suse.com
Subject: Re: reiserfs broke between 4.9.205 and 4.9.208
Date: Thu, 9 Jan 2020 13:30:41 +0100 [thread overview]
Message-ID: <20200109123041.GA14075@netestate.de> (raw)
In-Reply-To: <20200109121216.GC22232@quack2.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Hello Jan,
On Thu, Jan 09, 2020 at 01:12:16PM +0100, Jan Kara wrote:
> Also Michael, I'd like to clarify: Does 'cp -a' return any error or is it
> just that the kernel is spewing these annoying warnings? Because from the
> code reading I'd think that it is only the kernel spewing errors but
> userspace should be fine...
Yes, 'cp -a' returns errors and files are owned by root instead of the correct
user after copying as root.
Regards,
Michael Brunnbauer
--
++ Michael Brunnbauer
++ netEstate GmbH
++ Geisenhausener Straße 11a
++ 81379 München
++ Tel +49 89 32 19 77 80
++ Fax +49 89 32 19 77 89
++ E-Mail brunni@netestate.de
++ https://www.netestate.de/
++
++ Sitz: München, HRB Nr.142452 (Handelsregister B München)
++ USt-IdNr. DE221033342
++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-01-09 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 19:36 reiserfs broke between 4.9.205 and 4.9.208 Michael Brunnbauer
2020-01-08 23:42 ` Randy Dunlap
2020-01-09 12:12 ` Jan Kara
2020-01-09 12:30 ` Michael Brunnbauer [this message]
2020-01-14 20:21 ` Michael Brunnbauer
2020-01-15 17:03 ` Jeff Mahoney
2020-01-15 17:39 ` Jeff Mahoney
2020-01-15 18:02 ` Jeff Mahoney
2020-01-20 15:03 Byron Stanoszek
2020-01-20 16:20 ` Jeff Mahoney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200109123041.GA14075@netestate.de \
--to=brunni@netestate.de \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=reiserfs-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).