kill -STOP mountd-pid && kill -STOP nfsd-pid \
&& fsck NFS-exported-mountpoint && \
kill -START nfsd-pid && kill -START mountd-pid
just a crazy idea, never tried it myself...
I'd hate to be on an NFS client though ;-)
Ast
On Sat, Oct 19, 2013 at 06:33:59PM +0200, Hauke Fath wrote:
> On Sat, 19 O
On Sun, 20 Oct 2013, matthew green wrote:
as part of the GCC 4.8 preparation work, we're seeing many new
warnings where variables are only used inside KASSERT(), but the
non-diag kernel builds trigger errors.
my solution, rather than marking these variables with __USE(),
is to change KASSERT(
[I tried to send this to mouse in private email, but he refuses to accept it]
> I'd have a close look at the containing directory.
[Asterisks denote information manually hidden for privacy.
The filenames, owner and group names all make sense.]
I=158304666 MODE=40770 SIZE=512
MTIME=Oct 18
> On a FFSv2/WAPBL file system successfully fsck -f'd less than two hours
> before, I got a "bad dir: mangled entry" panic.
> I fsck'd again, finding missing dot/dotdot entries [...]
> Just within minutes after going live again, I experienced the same panic,
> and fsck found missing dot/dotdot in
EF> Can there be some weird file system inconsistency fsck doesn't spot?
dM> Yes. Well, almost certainly.
So, in case we experience more panics under load on monday, would it make
sense to dump/newfs/restore the file system? I.e., can there be any
inconsistencies that "survive" a dump/restore?
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>EF> Can there be some weird file system inconsistency fsck doesn't spot?
>dM> Yes. Well, almost certainly.
>So, in case we experience more panics under load on monday, would it make
>sense to dump/newfs/restore the file system? I.e., c
>>> Can there be some weird file system inconsistency fsck doesn't spot?
>> Yes. Well, almost certainly.
> So, in case we experience more panics under load on monday, would it
> make sense to dump/newfs/restore the file system? I.e., can there be
> any inconsistencies that "survive" a dump/restor
On Tue, Oct 15, 2013 at 06:01:29PM -0300, Lourival Vieira Neto wrote:
> > Also, having to switch mentally between zero-based arrays in the kernel C
> > code and 1-based arrays in the Lua code make my head ache.
> It's something that doesn't bug me so much.. But, if necessary it
> could be changed t
2013/10/21 Marc Balmer :
> Am 20.10.13 22:02, schrieb Artem Falcon:
>
> [...]
>
>> Ok, here i have a clean diff. Sorry for the attach instead of inline.
>> By the way, do you want to move from malloc(9) to kmem(9) as
>> recommended? I may provide a draft version, if you're interested.
>
> Thank you
