I am seeing the subject message
ehci1: missed microframe, TT reset not implemented, hub might be inoperational
on occasion on my Lenovo S10 workstation. It seems to coincide with
the mouse not working (usb mouse, connected through a Raritan KVM). I
have had to reboot to get the mouse working -- r
I did it again. gmail is trying to teach an old dog a new trick
-- Forwarded message --
From: Donald Allen
Date: Tue, Dec 13, 2011 at 10:04 AM
Subject: Re: Lost file-system story
To: David Holland
On Tue, Dec 13, 2011 at 1:27 AM, David Holland wrote:
> On Mon, Dec
On Mon, Dec 12, 2011 at 3:10 PM, Greg A. Woods wrote:
> At Sun, 11 Dec 2011 23:23:33 -0500, Donald Allen
> wrote:
> Subject: Re: Lost file-system story
>>
>> How can you possibly say such a thing and hope to be taken seriously?
>> What you just said means that P(surv
On Mon, Dec 12, 2011 at 2:40 PM, Greg Troxel wrote:
>
> Andy Ruhl writes:
>
>> If solving your problem depends on sync frequency, I don't see why
>> this shouldn't be managed by some knob to twiddle. Given that the
>> crash scenario doesn't get worse depending on where the knob is or if
>> the cr
On Sun, Dec 11, 2011 at 9:53 PM, Greg A. Woods wrote:
> At Fri, 9 Dec 2011 22:12:25 -0500, Donald Allen
> wrote:
> Subject: Re: Lost file-system story
>>
>> On Fri, Dec 9, 2011 at 8:43 PM, Greg A. Woods wrote:
>> > At Fri, 9 Dec 2011 15:50:35 -0500, Donald Allen
>> More later ...
I installed OpenBSD 5.0 on the same machine, similar setup (all
filesystems noatime except /tmp and /home, which are both
async,noatime). I repeated my experiment -- wrote a new file in my
home directory, waited a few minutes, and killed the power. On reboot,
there were complaint
On Sun, Dec 11, 2011 at 11:44 AM, Joerg Sonnenberger
wrote:
> On Sun, Dec 11, 2011 at 11:32:51AM -0500, Donald Allen wrote:
>> On Sun, Dec 11, 2011 at 11:04 AM, Joerg Sonnenberger
>> wrote:
>> > On Sun, Dec 11, 2011 at 10:50:29AM -0500, Donald Allen wrote:
>> >
On Sun, Dec 11, 2011 at 11:04 AM, Joerg Sonnenberger
wrote:
> On Sun, Dec 11, 2011 at 10:50:29AM -0500, Donald Allen wrote:
>> I repeated the test without the sync, but waited 15 minutes after
>> creating the new file before killing the power. When the system came
>> up, I
On Sun, Dec 11, 2011 at 10:25 AM, Donald Allen wrote:
> I should have sent this to the mailing list as well as David. Google
> has fixed something that wasn't broke -- gmail. They've introduced a
> new UI that I haven't gotten used to yet ...
>
>
> -- Fo
I should have sent this to the mailing list as well as David. Google
has fixed something that wasn't broke -- gmail. They've introduced a
new UI that I haven't gotten used to yet ...
-- Forwarded message ------
From: Donald Allen
Date: Sun, Dec 11, 2011 at 10:23 AM
Su
On Fri, Dec 9, 2011 at 8:43 PM, Greg A. Woods wrote:
> At Fri, 9 Dec 2011 15:50:35 -0500, Donald Allen
> wrote:
> Subject: Re: Lost file-system story
>>
>> "does not guarantee to keep a consistent file system structure on the
>> disk" is what I expected fro
On Fri, Dec 9, 2011 at 4:33 PM, Brian Buhrow
wrote:
> Hello. Just for your edification, it is possible to break out of fsck
> mid-way and reinvoke it with fsck -y to get it to do the cleaning on its
> own.
This whole discussion, interesting though it may be, may have occurred
simply becau
On Sat, Dec 10, 2011 at 1:14 PM, Edgar Fuß wrote:
> My impression is that you are asking for the impossible.
>
> The underlying misconception (which I know very well for suffering from it
> myself) is that a filesystem aims at keeping the on-disc metadata consistent
> and that tools like fsck ar
, as we've been discussing.
> }
> } So I'd love it if my experience encourages someone to improve NetBSD
> } ffs and fsck to make use of async practical, perhaps by drawing on
> } what OpenBSD has done. I also realize that my situation is unusual,
> } and with resources being scarce, there are a lot more important things
> } to work on, that will affect a lot more people. But I'd at least like
> } to get it in the queue.
> }
> } /Don Allen
>>-- End of excerpt from Donald Allen
>
>
I just did a little experiment. I installed OpenBSD 5.0 on the same
machine where I had my adventure with NetBSD. This time, I broke up
the world into separate filesystems, which OpenBSD facilitates,
mounting only /home and /tmp async, noatime. All the others were
mounted softdep,noatime. I downloa
On Wed, Dec 7, 2011 at 9:58 AM, Ignatios Souvatzis wrote:
> On Tue, Dec 06, 2011 at 12:44:16PM -0500, Donald Allen wrote:
>> On Tue, Dec 6, 2011 at 11:58 AM, Thor Lancelot Simon wrote:
>> > On Tue, Dec 06, 2011 at 11:10:44AM -0500, Donald Allen wrote:
>> >>
>&
On Tue, Dec 6, 2011 at 11:58 AM, Thor Lancelot Simon wrote:
> On Tue, Dec 06, 2011 at 11:10:44AM -0500, Donald Allen wrote:
>>
>> 2. I'm a little bit surprised that the filesystem was as much of a
>> mess as it was.
>
> I'm not. You mounted the filesy
On Tue, Dec 6, 2011 at 11:10 AM, Donald Allen wrote:
[deleted]
> catastrophic consequences in the very rare case of someone doing what
> I did (mounting async, doing a lot of writing followed by a system
> crash). I'm trying to make the argument that there could be a problem
>
I recently installed NetBSD 5.1 on an old Thinkpad T41 that I use for
experimentation. I installed it with a single, monolithic filesystem,
which I mounted async,noatime. Yes, I'm fully aware that's dangerous
and was aware of it at the time. But I have a long history of
running Linux systems w
19 matches
Mail list logo
