> Just a reminder. fsck is responsible for applying the journal to
> journaled filesystems. So you really do want it to run everytime.
I'm confused by this. Mount claims that it replays journals by giving
you the hazardous option of preventing it:
"norecovery/noload
Don't load the journal
Just a reminder. fsck is responsible for applying the journal to
journaled filesystems. So you really do want it to run everytime.
This discussion should be about controlling the "full" fsck that
happens if requested or if the mount count or time exceeds it's
limit. These are all controlled out
rlfrost writes:
> I am not sure what to make of this, but the data must surely be useful
> to the Debian team.
Please file a bug report so that the team will actually get it.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
w
I read this entire thread, and I just wanted to add to the mix, because
I am seeing a similar phenomenon on a very new quad core (intel) box
with no disk encryption whatsoever. I don't have a lot of information
yet, because I had attributed this issue to Jessie not being quite ready
for prime
On 01/07/2015 01:45 PM, Bob Proulx wrote:
> The Wanderer wrote:
>> To my eye, based on what you've reported, it does look as if the reason
>> your system is running fsck on every boot is that something about a
>> mount attempt is failing. However, aside from "probably to do with the
>> swap partiti
On 01/07/2015 08:16 AM, The Wanderer wrote:
> On 01/07/2015 at 08:39 AM, ~Stack~ wrote:
>
[snip]
>> However, I
>> *have* read the man page and the man page for fstab says "If the
>> sixth field is not present or zero, a value of zero is returned and
>> fsck will assume that the filesystem does n
Greetings,
On 01/07/2015 11:06 AM, Rob Owens wrote:
> I suppose it's possible that the bios battery is no good, and the clock
> is getting reset after each shutdown. Then the "last time fsck'd" would
> be in the future, and I expect the system might fsck your disk as a
> precaution.
>
> You mig
The Wanderer wrote:
> To my eye, based on what you've reported, it does look as if the reason
> your system is running fsck on every boot is that something about a
> mount attempt is failing. However, aside from "probably to do with the
> swap partition", I have no clue what that something is - or
On Tue, Jan 06, 2015 at 06:23:18PM -0600, ~Stack~ wrote:
> Greetings,
>
> This problem has been a minor annoyance for a while but only recently
> have I started to use Jessie more and it is has finally peeved me off. I
> have been trying everything I can find for the last two hours and I
> still c
do u have a "fsck" file in the root / of the partition?
(this will cause a fs check as well)
mvg,
Wim
On Tue, 2015-01-06 at 18:23 -0600, ~Stack~ wrote:
> Greetings,
>
> This problem has been a minor annoyance for a while but only recently
> have I started to use Jessie more and it is has finally
On 01/07/2015 at 08:39 AM, ~Stack~ wrote:
> On 01/07/2015 03:10 AM, Ric Moore wrote:
>
>> On 01/06/2015 07:23 PM, ~Stack~ wrote:
>>
>>> I keep seeing all of these posts online saying how easy it is to
>>> disable systemd from runing fsck because it "honors" the '0' in
>>> the sixth field of /etc
On 01/07/2015 05:21 AM, Martin Steigerwald wrote:
> Am Dienstag, 6. Januar 2015, 22:13:26 schrieb ~Stack~:
>> In summary:
>> * I have systemd-fsck disabled just about every damn place I can find to
>> do so, yet it still runs on boot every time. I see it on the screen and
>> in the log messages.
>>
On 01/07/2015 03:10 AM, Ric Moore wrote:
> On 01/06/2015 07:23 PM, ~Stack~ wrote:
>
>> I keep seeing all of these posts online saying how easy it is to disable
>> systemd from runing fsck because it "honors" the '0' in the sixth field
>> of /etc/fstab. Well that's just pure bull$h1t... That was on
Am Dienstag, 6. Januar 2015, 22:13:26 schrieb ~Stack~:
> In summary:
> * I have systemd-fsck disabled just about every damn place I can find to
> do so, yet it still runs on boot every time. I see it on the screen and
> in the log messages.
> * I still can't find where the hell systemd stores the s
On 01/06/2015 07:23 PM, ~Stack~ wrote:
I keep seeing all of these posts online saying how easy it is to disable
systemd from runing fsck because it "honors" the '0' in the sixth field
of /etc/fstab. Well that's just pure bull$h1t... That was one of the
first things I tried some time ago. As far
Greetings,
On 01/06/2015 07:56 PM, Patrick Bartek wrote:
> Have you tried tune2fs on each partition?
>
>http://crashmag.net/disable-filesystem-check-fsck-at-boot-time
I did and that didn't help either.
After I sent my plea for help, I took a break to grab some dinner and
chill. When I retu
On Tue, 06 Jan 2015, ~Stack~ wrote:
> Greetings,
>
> This problem has been a minor annoyance for a while but only recently
> have I started to use Jessie more and it is has finally peeved me
> off. I have been trying everything I can find for the last two hours
> and I still can't get systemd to
17 matches
Mail list logo
