On 2015-11-28 11:52, Jeff Mahoney wrote:
On 11/23/15 11:02 PM, Christoph Anton Mitterer wrote:
Hey.
Short question since that came up on debian-devel.
Now that btrfs check get's more and more useful, are the
developers going to recommend running it periodically on boot (of
course that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/29/15 8:59 PM, Qu Wenruo wrote:
>
>
> Jeff Mahoney wrote on 2015/11/28 11:52 -0500: On 11/23/15 11:02
> PM, Christoph Anton Mitterer wrote:
Hey.
Short question since that came up on debian-devel.
Now that btrfs check
Jeff Mahoney wrote on 2015/11/28 11:52 -0500:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/23/15 11:02 PM, Christoph Anton Mitterer wrote:
Hey.
Short question since that came up on debian-devel.
Now that btrfs check get's more and more useful, are the
developers going to recommend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/23/15 11:02 PM, Christoph Anton Mitterer wrote:
> Hey.
>
> Short question since that came up on debian-devel.
>
> Now that btrfs check get's more and more useful, are the
> developers going to recommend running it periodically on boot (of
>
Am Mittwoch, 25. November 2015, 07:32:34 CET schrieb Austin S Hemmelgarn:
> On 2015-11-24 17:26, Eric Sandeen wrote:
> > On 11/24/15 2:38 PM, Austin S Hemmelgarn wrote:
> >> if the system was
> >> shut down cleanly, you're fine barring software bugs, but if it
> >> crashed, you should be running a
On 2015-11-24 17:26, Eric Sandeen wrote:
On 11/24/15 2:38 PM, Austin S Hemmelgarn wrote:
if the system was
shut down cleanly, you're fine barring software bugs, but if it
crashed, you should be running a check on the FS.
Um, no...
The *entire point* of having a journaling filesystem is that
On Tue, Nov 24, 2015 at 04:26:47PM -0600, Eric Sandeen wrote:
> On 11/24/15 2:38 PM, Austin S Hemmelgarn wrote:
>
> > if the system was
> > shut down cleanly, you're fine barring software bugs, but if it
> > crashed, you should be running a check on the FS.
>
> Um, no...
>
> The *entire point*
On Tue, 2015-11-24 at 22:33 +, Hugo Mills wrote:
> whereas a read-only mount of a journalling FS _must_ modify the disk
> data after an unclean shitdown, in order to be useful (because the FS
> isn't consistent without the journal replay).
I've always considered that rather a bug,... or at
Hugo Mills wrote on 2015/11/24 22:33 +:
On Tue, Nov 24, 2015 at 04:26:47PM -0600, Eric Sandeen wrote:
On 11/24/15 2:38 PM, Austin S Hemmelgarn wrote:
if the system was
shut down cleanly, you're fine barring software bugs, but if it
crashed, you should be running a check on the FS.
Um,
On Wed, Nov 25, 2015 at 12:01:49AM +0100, Christoph Anton Mitterer wrote:
> On Tue, 2015-11-24 at 22:33 +, Hugo Mills wrote:
> > whereas a read-only mount of a journalling FS _must_ modify the disk
> > data after an unclean shitdown, in order to be useful (because the FS
> > isn't consistent
On 2015-11-24 12:23, Christoph Anton Mitterer wrote:
On Tue, 2015-11-24 at 11:14 -0600, Eric Sandeen wrote:
In a nutshell, though, I think a filesystem repair should be an
admin-initiated
action, not something that surprises you on a boot, at least for a
journaling
filesystem which is designed
On Tue, 2015-11-24 at 11:14 -0600, Eric Sandeen wrote:
> In a nutshell, though, I think a filesystem repair should be an
> admin-initiated
> action, not something that surprises you on a boot, at least for a
> journaling
> filesystem which is designed to maintain its integrity even in the
> face
On 11/24/15 12:56 AM, Duncan wrote:
> Duncan posted on Tue, 24 Nov 2015 06:46:18 + as excerpted:
>
>> That wouldn't be entirely uncommon, because as Eric mentions, btrfs
>> check is intended to be thorough, where the kernel mount-time check is
>> intended to be fast.
>>
>> But of course, as
On 11/24/15 2:38 PM, Austin S Hemmelgarn wrote:
> if the system was
> shut down cleanly, you're fine barring software bugs, but if it
> crashed, you should be running a check on the FS.
Um, no...
The *entire point* of having a journaling filesystem is that after a
crash or power loss, a journal
On Tue, Nov 24, 2015 at 12:02 PM, Christoph Anton Mitterer
wrote:
> Hey.
>
> Short question since that came up on debian-devel.
>
> Now that btrfs check get's more and more useful, are the developers
> going to recommend running it periodically on boot (of course that
>
On 11/23/15 10:35 PM, Duncan wrote:
> Christoph Anton Mitterer posted on Tue, 24 Nov 2015 05:02:34 +0100 as
> excerpted:
>
>> Hey.
>>
>> Short question since that came up on debian-devel.
>>
>> Now that btrfs check get's more and more useful, are the developers
>> going to recommend running it
On Tue, 2015-11-24 at 04:35 +, Duncan wrote:
> I'm a list regular and btrfs user, not a dev, but all the indications
> continue to point to _not_ running it automatically at boot, nobody
> even
> _suggesting_ otherwise.
Sure, I just asked because maybe that would have just been an
Christoph Anton Mitterer posted on Tue, 24 Nov 2015 05:02:34 +0100 as
excerpted:
> Hey.
>
> Short question since that came up on debian-devel.
>
> Now that btrfs check get's more and more useful, are the developers
> going to recommend running it periodically on boot (of course that
> wouldn't
Christoph Anton Mitterer wrote on 2015/11/24 05:43 +0100:
On Tue, 2015-11-24 at 04:35 +, Duncan wrote:
I'm a list regular and btrfs user, not a dev, but all the indications
continue to point to _not_ running it automatically at boot, nobody
even
_suggesting_ otherwise.
Sure, I just
Christoph Anton Mitterer posted on Tue, 24 Nov 2015 05:43:31 +0100 as
excerpted:
[Duncan wrote...]
>> The btrfs kernel code itself detects and often
>> corrects many problems, and btrfs check is simply not recommended for
>> automatic at-boot scheduling -- if the kernel code can't fix it without
Duncan posted on Tue, 24 Nov 2015 06:46:18 + as excerpted:
> That wouldn't be entirely uncommon, because as Eric mentions, btrfs
> check is intended to be thorough, where the kernel mount-time check is
> intended to be fast.
>
> But of course, as Eric also mentions, that's yet another reason
Hey.
Short question since that came up on debian-devel.
Now that btrfs check get's more and more useful, are the developers
going to recommend running it periodically on boot (of course that
wouldn't work right now, as it would *always* check)?
Plus... is btrfs check (without any arguments)
22 matches
Mail list logo