lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: mountall (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Based on the bug comment history, I don't believe there are any further
changes to be made to mountall here. If I've overlooked something,
please reopen.
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
OK, that makes sense. I had assumed this was a check-only pass through
fstab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575293
Title:
mountall trying to check mounts with pass=0
To manage
The original problem, though sadly I did not post the exact messages,
was saying it could not run fsck.cifs (which of course is non-existent).
The bug in this case was that with pass=0 it should not even have tried
to run a check on boot-up.
The bug now is the same underlying problem, that during
The current (64-bit 10.04) boot.log file has messages such as these
appearing:
error -1 (Unknown error 18446744073709551615) opening credential file
/home/paul/.smbcredentials
mountall: mount /media/swdev [1087] terminated with status 1
mount error: could not resolve address for smb: Temporary
Ok; the error message for fsck.cifs has been resolved now via bug
#838091. I don't know if mountall is still trying to find fsck for
filesystems with pass=0 set - it's not meant to, and the code is written
to specifically avoid fscking them.
The bug now is the same underlying problem, that
oops, I think that 'task' bit in the sample upstart job is wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575293
Title:
mountall trying to check mounts with pass=0
To manage notifications
The bug description talks about checking mounts with pass=0; but the log
output included in the bug shows errors when trying to *mount* the cifs
mounts. What exactly is the problem you're experiencing?
** Changed in: mountall (Ubuntu)
Status: Confirmed = Incomplete
--
You received this
** Changed in: mountall (Ubuntu Lucid)
Assignee: Canonical Foundations Team (canonical-foundations) = James Hunt
(jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575293
Title:
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
** Also affects: mountall (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu Lucid)
Importance: Undecided = Low
** Changed in: mountall (Ubuntu Lucid)
Status: New = Confirmed
**
It seems my system has been updated to 2.15 but there are still the odd
warnings about CIFS mounts in fstab
Also the stage 2 of 3 pass had no text on the plymouth screen, but it came back
for stage 3 of 3.
--
mountall trying to check mounts with pass=0
https://bugs.launchpad.net/bugs/575293
mountall 2.15 is available as a backport to 10.04 LTS.
Try apt or synaptic.
Dev group is working on (at least) mountall 2.5, but I don't know where you'd
get that.
I don't know if either of these will help, but it may be worth a try at least
for 2.15
--
mountall trying to check mounts with
Forget the previous mountall 2.5 comment, that's a much earlier version
of mountall.
I'm not happy that mountall 2.15 forces long-winded fscks of presumably
clean ext3 partitions. In my case, it's a trivial two-minute wait, once
every 20 mounts, but I don't think this delay should be there for a
Tested again with updates from Arand's unstable PPA for plymouth and
mountall (though mountall --version still says 2.14!?) and it still
complains about CIFS mounts when I forced a check of file systems:
sudo touch /forcefsck
reboot
boot.log shows:
fsck from util-linux-ng 2.17.2
/dev/sda7:
14 matches
Mail list logo
