fsck.btrfs is now just a dummy program to return exit code 0.
Source: $ man fsck.btrfs
** Changed in: btrfs-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a memb
I really don't want to special case btrfs.
But I see that with very large hard-drives it can be a pain.
Note, that earlier mentions of ext4 do not apply here as most of the time it,
fsck on ext4 quits reporting filesystems as clean.
Maybe a configuration options should be included to prevent inclu
If you read the btrfsck manual even in quantal, you will see:
"Btrfs is currently under heavy development, and not suitable for any
uses other than benchmarking and review."
I took that into consideration before working around the long scan at boot.
Anyone that is using btrfs is clearly experim
Curtis Lee Bolin, quantal has much newer btrfs-tool, which have newer
fsck tool. If it is still so slow for you, the best procedure is to
request the upstream btrfsck to support standard flags of checking if
the disk is dirty/fsck not run in a while and only then spend 9 minutes
fscking. Are you wi
Dmitrijs Ledkovs, you are absolutely correct that this is not a Linux kernel
bug, but Quantal is still currently using Btrfs v0.19 with the same btrfsck.
With my 3TB fs, it takes about 9 minutes to boot because of the fs check.
--
You received this bug notification because you are a member of
Please correct, if I am wrong, but this is not a linux kernel bug, as
far as I can see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771748
Title:
Ubuntu does fsck on every start when using btrfs
Well btrfsck does do something useful in Quantal...
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771748
Title:
Ubuntu does fsck on
A quick work around if the bootup speed is really killing you and since btrfsck
doesn't do much yet.
Please realize this prevents mountall from running btrfsck and this is NOT a
fix.
You can move btrfsck somewhere where you can still use it:
$ sudo mv /sbin/btrfsck /usr/local/bin/
Then make a s
1 year. Nothing changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771748
Title:
Ubuntu does fsck on every start when using btrfs
To manage notifications about this bug go to:
https://bugs.laun
** Changed in: btrfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771748
Title:
Ubuntu does fsck on every start when using btrfs
To manage notificati
This is not a bug in mountall. fsck is meant to be called for all
filesystems at boot, and it's the responsibility of the per-filesystem
fsck implementation to figure out if the filesystem is clean or if
something needs to be done. If fsck.btrfs doesn't provide the standard
interface for fsck, tha
After few months btrfs crashes so badly, that I cannot access my /home
folder. Btrfsck finds an error but seems it cannot repair it. (bug
#804309)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771748
OK, then mountall is the offender here, because that's what
/etc/init/mountall.conf calls. According to its manpage it runs fsck.
** Also affects: mountall (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There's actually a very simple fsck for btrfs (btrfsck), but it's very
primitive and doesn't support any of the command line options yet.
Maybe something calls it, and expects it to support some command line
option? Something like --dont-run-every-time, except with a different
name of course.
--
Seems to concern only systems with a btrfs partition regardless of mount
point. It might be because there is no fsck tool for btrfs!
** Summary changed:
- Ubuntu does fsck on every start
+ Ubuntu does fsck on every start when using btrfs
--
You received this bug notification because you are a m
15 matches
Mail list logo
