From: Lionel Bouton <lionel-subscription@bouton.name>
To: covici@ccs.covici.com
Cc: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs says no errors, but booting gives lots of errors
Date: Sun, 11 Oct 2015 01:58:13 +0200 [thread overview]
Message-ID: <5619A615.3090503@bouton.name> (raw)
In-Reply-To: <28329.1444519978@ccs.covici.com>
Le 11/10/2015 01:32, covici@ccs.covici.com a écrit :
> [...]
> I don't know if the file in question had the correct data, I only did a
> directory listing, but this makes no sense -- I did an rsync just before
> booting and got all kinds of errors and the only difference is the file
> system, this is what I am saying.
What makes no sense is that the same filesystem both shows the file is
there and isn't. If there was data corruption or buggy behaviour at
least it should be somehow consistent.
What is more likely is that the rsync was incomplete and didn't transfer
some data needed by systemd: did you transfer (from the top of my head)
extended attributes, special files, device files ? By default rsync
doesn't do that.
Lionel
next prev parent reply other threads:[~2015-10-10 23:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 12:46 btrfs says no errors, but booting gives lots of errors covici
2015-10-10 14:12 ` Holger Hoffstätte
2015-10-10 14:41 ` covici
2015-10-10 15:46 ` Lionel Bouton
2015-10-10 16:10 ` Holger Hoffstätte
2015-10-10 16:55 ` covici
2015-10-10 22:04 ` Lionel Bouton
2015-10-10 23:02 ` covici
2015-10-10 23:08 ` covici
2015-10-11 12:13 ` Duncan
2015-10-11 12:29 ` covici
2015-10-15 2:10 ` Duncan
2015-10-10 23:21 ` Lionel Bouton
2015-10-10 23:32 ` covici
2015-10-10 23:58 ` Lionel Bouton [this message]
2015-10-11 0:28 ` covici
2015-10-10 16:45 ` covici
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=5619A615.3090503@bouton.name \
--to=lionel-subscription@bouton.name \
--cc=covici@ccs.covici.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@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).