to breadn will clear up Greg's
problem with NFS.
Kirk
=-=-=-=-=-=-=-=
To: Kirk McKusick <[EMAIL PROTECTED]>
Cc: Julian Elischer <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]>,
Alan Cox <[EMAIL PROTECTED]>, Mike Smith <[EMAIL PROTECTE
the following patch to see if it helps. It is
making use of BUF_KERNPROC for cases in which it is not
intended, but if it gets around your current problem, then
gives a good indication of what to look for as a real fix.
Kirk McKusick
Index: vm_pager.c
ssing BUF_KERNPROC in the paging
code, so I am hopeful that he can apply his wizardry here as
well. If the problem has not been resolved by the time of my
return (August 30th) I promise to track down the problem on
my return.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
. Does anyone on this list know of any
programs that need/want the block interface? If there are none, or
only very obscure ones, then it seems pointless to waste any kernel
code supporting them. Indeed it will clean up a good deal of code
to get rid of them.
Kirk McKusick
To Unsubscribe: send
machines, then you would need to have some central
coordinator running some sort of coherency protocol with a complexity
akin to that of NFS.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: Mike Smith <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: Mounting one FS on more than one system
In-reply-to: Your message of "Sat, 04 Dec
To: [EMAIL PROTECTED]
Subject: HEADSUP: bioops patch.
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
Date: Wed, 14 Jun 2000 22:29:32 +0200
This patch virtualizes & untangles the bioops operations vector.
Background:
The bioops operation vecto
than the one you are reporting, it may be
related. I suggest that you update to the above delta and see if it
solves your problem. If your problem persists, let me know. As always,
if you can give a specific set of inputs which trigger the problem,
that is always helpful in tracking it down.
t is just one more bit of trivia that
new system administrators need to learn to make their systems run
well. The more of those details that need not be learned because
they just do the right thing, the better.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
PROTECTED]`--'
The above explanation is correct. When I made the change to allow
recursive buffer locks, I should have removed that panic (but forgot
that I had put it in there, sigh). I have just made the change on
freefall. Sorry for the proble
I have (finally) found and fixed this problem. You need to get
version 1.107 or later of /sys/ufs/ffs/ffs_softdep.c (2002/02/07).
Kirk McKusick
=-=-=-=-=-=
Date: Tue, 28 Aug 2001 14:02:24 +0200
From: Ollivier Robert <[EMAIL PROTECTED]>
To: "FreeBSD Current Users
I have (finally) found and fixed this problem. You need to get
version 1.107 or later of /sys/ufs/ffs/ffs_softdep.c (2002/02/07).
Kirk McKusick
=-=-=-=-=-=
Date: Tue, 28 Aug 2001 14:02:24 +0200
From: Ollivier Robert <[EMAIL PROTECTED]>
To: "FreeBSD Current Users
Date: Sun, 25 Mar 2001 11:20:17 +0200
From: Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>,
Peter Wemm <[EMAIL PROTECTED]>,
Paul Saab <[EMAIL PROTECTED]>, Matt Dillon <[EMAIL PROTECTED]&
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: fsdb broken in -current
Date: Mon, 23 Apr 2001 22:23:48 +0100
From: Ian Dowse <[EMAIL PROTECTED]>
The last set of changes to fsck_ffs moved the initialisation of
aces it with code to find
and delete the newdirblk dependency so that the truncation can
succeed. This delta should clear up the recent problems that
folks have been having with soft updates.
Kirk McKusick
=-=-=-=-=
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: worklist_remove pa
To: Michael Harnois <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: filesystem errors
In-Reply-To: Your message of "Wed, 25 Jul 2001 23:14:16 CDT."
<[EMAIL PROTECTED]>
Date: Thu, 26 Jul 2001 15:14:09 +0100
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
Ollivier Robert <[EMAIL PROTECTED]>,
Mikhail Teterin <[EMAIL PROTECTED]>
Subject: fsck setting d_ino == 0 (was Re: filesystem errors)
In-Reply-T
r_rman.c
I have checked in revision 1.15 for subr_rman.c which should fix
the problems being experienced with version 1.14. If you continue
to experience problems with version 1.15, please let me know.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
Jeffrey Hsu and I just came to the same conclusion about the splbio
additions earlier this week. I had assumed that Jeffrey had put in
these changes already. Anyway, the two of you need to coordinate
getting the changes put in so that you do not collide.
Kirk McKusick
es dumps. This setuid program could
then be invoked by dump -L to create a snapshot for it. I favor
the first approach, but there may be good security issues of which
I am unaware that make that a bad choice. Perhaps we could get
someone like Robert Watson to comment on these choices.
Kirk M
Date: Fri, 31 Jan 2003 02:24:00 +0200
From: Giorgos Keramidas <[EMAIL PROTECTED]>
To: Garrett Wollman <[EMAIL PROTECTED]>
Cc: Kirk McKusick <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: dump -L and privilege
X-ASK-
From: Jun Kuriyama <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: dump -L and privilege
In-Reply-To: <[EMAIL PROTECTED]>
X-ASK-Info: Whitelist match
Is this enough?
.
Kirk McKusick
=-=-=-=-=-=
Date: Fri, 14 Feb 2003 15:54:13 -0800
From: Kris Kennaway <[EMAIL PROTECTED]>
To: Kris Kennaway <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: INVARIANTS-related fs panic on alpha
On Sat, Jan
ady existing inode (3
which was presumably the usr directory in the original dump).
Neither of these are problematic or affected your restore.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Date: Sat, 15 Feb 2003 00:50:01 +0100 (CET)
From: Martin Blapp <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Kirk McKusick <[EMAIL PROTECTED]>
Subject: Reboot(8) when fsck_ufs is running ?
Hi all,
I don't know what the be
From: David Syphers <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Subject: Re: BOOT2_UFS=UFS1_ONLY works for today's current
Date: Sun, 23 Feb 2003 14:49:52 -0600
Cc: [EMAIL PROTECTED]
On Sunday 23 February 2003 11:10 a
> Date: Wed, 1 Dec 2010 16:27:48 +0200
> From: Kostik Belousov
> To: Peter Holm
> Cc: Garrett Cooper ,
> Marshall Kirk McKusick , curr...@freebsd.org
> Subject: Re: How a full fsck screwed up my SU+J filesystem
>
> On Wed, Dec 01, 2010 at 12:00:08PM +0100, Pete
0 owned by root, then create the snapshot as say
/export/.snap/snap1. This way, it will be out of the way of all
snoopy programs except those walking the filetree as root.
Kirk McKusick
Results of my test -
Script started on Fri Aug 22 17:18:34 2003
tank#
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: "[iso-8859-2] Branko F. Graènar" <[EMAIL PROTECTED]>,
Paul Saab <[EMAIL PROTECTED]>,
Robert Watson <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subjec
the high-end IDE disks.
Kirk McKusick
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
I have been able to reproduce your hang on my system and your suggested
fix does prevent it. I am going to run some more buffer starvation-type
tests on it this week and if they do not cause other problems, I will
put in your suggested fix.
Kirk McKusick
=-=-=-=-=-=
To: [EMAIL PROTECTED
> To: Kirk McKusick <[EMAIL PROTECTED]>
> From: "Brian F. Feldman" <[EMAIL PROTECTED]>
> Date: Thu, 23 Oct 2003 15:46:53 -0400
> Cc: [EMAIL PROTECTED]
> Subject: Re: runningbufspace related lock-ups with md(4)/UFS/SU (PATCH ?)
>
> Kirk McKusick <[EM
l not know about the new system
calls that support the new statfs structure. Running an old kernel
after a `make world' will cause programs such as `df' that do a
statfs system call to fail with a bad system call.
Kirk McKusick
___
[
> Date: Fri, 14 Nov 2003 08:33:06 +
> From: Matt Smith <[EMAIL PROTECTED]>
> To: Marco Wertejuk <[EMAIL PROTECTED]>
> Cc: Kirk McKusick <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: HEADS-UP new statfs structure
> X-ASK-Info: Whitelist match
>
your kernel.
Kirk McKusick
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
This error happens if things are not properly locked. As per my
previous message, I am not able to look at it now, but am hoping
that resolving some of the other races will solve this as well.
Kirk McKusick
___
[EMAIL PROTECTED] mailing list
ecent rework (1.24). If that version has the problem as well, then
I believe that some other change is triggering the problem, as 1.24
represents a version that has been in production for half a year
without trouble.
Kirk McKusick
=-=-=-=-=-=-=-=
Date: Sun, 9 May 1999 01:39:33 -0700 (PDT)
list email and emailing me directly will
ensure the quickest response.
Special thanks to John Kozubik of rsync.net for getting me
interested in pursuing 64-bit quota support and for funding
part of my development time on this project.
Kirk McKusick
ng until you run
the fsck.
Kirk McKusick
=-=-=-=-=-=-=
golf# uname -a
FreeBSD golf.macomnet.net 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #19: Thu Feb 27
13:33:49 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
golf# fsck /dev/ad0s2a
** /dev/ad0s2a
** Last Mounted on /mnt
**
ng by using `fsck -b16 ...' to override the integrity check.
Given that you have had the problem, I expect that others will as well,
so I will make a note in the UPDATING notes to suggest the use of
`fsck -b16 ...' when going back to using filesystems on 4.X systems.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
d by: Poul-Henning Kamp <[EMAIL PROTECTED]>
Reviewed by:Maxime Henrion <[EMAIL PROTECTED]>
----
Kirk McKusick
=-=-=-=-=-=
To: [EMAIL PROTECTED]
Subject: UFS2 related message?
Date: Sat, 22 Jun 2002 20:45:01 +0900
From: Munehiro Matsuda <[EMAIL
I have put a fix in /sys/ufs/ufs/ufs_inode.c (on freefall) which
should solve this panic.
Kirk McKusick
=-=-=-=
From: Wesley Morgan <[EMAIL PROTECTED]>
Date: Mon, 24 Jun 2002 18:04:07 -0400 (EDT)
Subject: -current panic in suser_cred()
To: <[EMAIL PROTECTED]>
At some poin
superblock with UFS1 inode blocks when you
created the UFS1 filesystem. I had originally put code in to
stomp out all other possible superblock locations when creating
a filesystem in newfs, but got in trouble as I ended up stomping
on boot block information that UFS2 filesystems place where the
UFS1 s
http://www.freebsd.org/~mckusick/UFS2_update.diffs
The program `zapsb.c' that reverts a UFS2 filesystem to its
previous state can be found at:
http://www.freebsd.org/~mckusick/zapsb.c
If this change is going to cause you undue hardship, please
send me mail ([EMAIL PROTECTED]).
Kir
, but not at this
point in time when we are trying to keep changes to a minimum
and do not have time for extensive testing.
Kirk McKusick
=-=-=-=-=
Date: Sun, 24 Nov 2002 21:28:38 -0800 (PST)
From: Julian Elischer <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMA
Date: Mon, 25 Nov 2002 01:08:30 -0800 (PST)
From: Julian Elischer <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], Robert Watson <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Update to UFS2
superblock magic
number. Had you mounted it before running the new fsck, all would
have been well. I am at a loss to explain why fsck did not gag
and refuse to check it though.
Kirk McKusick
=-=-=-=-=
Date: Thu, 28 Nov 2002 06:01:36 + (GMT)
From: Daniel Flickinger <[EMAIL PROTECTED]&
o fix
problems with UFS2 before most people had deployed it. From
here on out, I promise not to introduce major breakage :-)
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
update to ufs/ffs/ffs_vfsops.c (version 1.198) that
explicitly checks to make sure that it will not trash your disk
label. I highly recommend that you update to this version, even if
you are only running with UFS1 filesystems.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Date: Fri, 29 Nov 2002 14:53:06 -0500 (EST)
From: Wesley Morgan <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: Trashed Disk Labels
X-ASK-Info: Confirmed by User
On Fri, 29 Nov 2002, K
Date: Sat, 30 Nov 2002 17:43:53 +1100 (EST)
From: Bruce Evans <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: Trashed Disk Labels
In-Reply-To: <[
correct me if I am incorrect
on this point.
Kirk McKusick
=-=-=-=-=-=
Date: Fri, 29 Nov 2002 22:57:12 -0800
To: Kirk McKusick <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
From: Manfred Antar <[EMAIL PROTECTED]>
Subject: Re: Update to UFS2 Superblock Format
Cc: Robert Watson <[
Date: Fri, 29 Nov 2002 23:16:51 -0800
To: Kirk McKusick <[EMAIL PROTECTED]>
From: Manfred Antar <[EMAIL PROTECTED]>
Subject: Re: Update to UFS2 Superblock Format
Cc: [EMAIL PROTECTED], Robert Watson <[EMAIL PROTECTED]>,
[EMAI
ached
In-Reply-To: <[EMAIL PROTECTED]>
I don't have time to test this right now, but see also PR bin/30959.
Ceri
--
you can't see when light's so strong
you can't see when light is gone
Better late than never, this bug ha
Your deadlock should now be fixed.
Kirk McKusick
=-=-=-=-=
From: Kirk McKusick <[EMAIL PROTECTED]>
Date: Fri, 29 Nov 2002 23:27:12 -0800 (PST)
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: cvs commit: src/sys/ufs/ffs ffs_snapshot.c
X-FreeBSD-CVS-Branch: HEAD
mckusick2002
nce you have done that, you
will be able to unmount it and run the new fsck. Similarly, if you
have an older kernel (vintage last four months of -current) then it
will back-convert your UFS2 filesystems every time you run it and thus
you will have to forward convert before fsck will run on it aga
sts.
The only problem that I am having with 5.0 as of last night
is getting login to work on my console.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
`ps axl'? If not, can you break into
the debugger and get a ps output? (You will need to have the DDB
option specified in your config file).
Kirk McKusick
=-=-=-=-=-=
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Nate Lawson <[EMAIL PROTECTED]>
Date: Fri, 6 Dec 2002 10:57:13 -0800 (PST)
CC: Kirk McKusick
tp://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
If the 1.17.2.4 commit does not solve your problem, try the following
patch that I made to the 5.0 fsck. If it solves your problem, then it
should probably be MFC'ed.
Kirk McKu
x27;s, then there is
still a good reason not to use soft updates on the root filesystem.
Kirk McKusick
=-=-=-=-=
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Dan Nelson <[EMAIL PROTECT
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Date: Fri, 6 Dec 2002 13:01:20 -0800 (PST)
CC: Archie Cobbs <[EMAIL PROTECTED]&
I suggest that we drag Thomas-Henning von Kamptz into this
discussion as he was one of the main authors of growfs. He
is copied on my reply.
Kirk McKusick
=-=-=-=-=-=
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: &
From: Archie Cobbs <[EMAIL PROTECTED]>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Date: Fri, 6 Dec 2002 15:23:36 -0800 (PST)
CC: Archie Cobbs <[EMAIL PROTECTED]&
Adding a two minute delay before starting background fsck
sounds like a very good idea to me. Please send me your
suggested change.
Kirk McKusick
=-=-=-=-=
Date: Fri, 6 Dec 2002 10:44:45 -0800
From: Brooks Davis <[EMAIL PROTECTED]>
To: Nate Lawson <[EMAIL PROTECTED]>
Cc: K
Thanks for reminding me about your userland change to background
fsck. I have tried it out and concur that it is the right approach
until we manage to get the general solution in the kernel. I
suggest that you propose it to release engineering and if approved
check it in.
Kirk McKusick
need to be updated
for ufs2?
-Nate
I have made the structural changes to growfs to make it work for
UFS2, however, I have not done more than cursory testing. I would
appreciate it if someone could try running it on various UFS2
filesystems to see if it works properly.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In theory the MNT_RELOAD command should reload all the filesystem
metadata properly though this feature has not been tested with
growfs. If anyone has the time to try it out and report back any
problems, that would be appreciated.
Kirk McKusick
=-=-=-=-=
From: Archie Cobbs <[EM
those out of range blocks
were allocated.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
14, 2002. Please verify that you are
running with this version. If you had this problem after that
conversion please contact me directly so I can try and work out
more of the details.
Kirk McKusick
=-=-=-=-=-=
Date: Sat, 14 Dec 2002 21:47:20 +0100 (CET)
From: Martin Blapp <[EM
g and copying an alternate into
the standard location is losing the update done for the size field.
I am not sure how that is happening, but I am hoping to catch
where in all your messing around with alternates that is happening
so I can cover that hole.
Kirk McKusick
=-=-=-=-=-=
Date: Tue, 1
fixed on a post 12/15 system, it should not recur.
You can avoid the panic by running `fsck -f -p' on all your system
after upgrading to a post 12/15 system. If you find continued
evidence of trouble after following the above procedures, please
send me mail.
Kirk McKusick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Date: Mon, 9 Dec 2002 11:19:13 -0800
From: Brooks Davis <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTECTED]>
Cc: Brooks Davis <[EMAIL PROTECTED]>, Nate Lawson <[EMAIL PROTECTED]>,
Archie Cobbs <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
I corrected a botched patch last night. Make sure that you are running
with version 1.56 2002/12/18 07:19:41 of ufs/ffs/ffs_snapshot.c.
Kirk McKusick
=-=-=-=-=
Date: Wed, 18 Dec 2002 11:43:25 +0100
From: Aurelien Nephtali <[EMAIL PROTECTED]>
To: Kirk McKusick <[EMAIL PROTE
I have managed to panic my system on a hard reboot and now believe
that I have found the problem on which you are faulting. I have
checked in a fix to the head of the tree (sys/ufs/ffs/ffs_snapshot.c
version 1.57). Let me know if it fixes your problem.
Kirk McKusick
To Unsubscribe: send
the same code running in fsck does not.
Kirk McKusick
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Thanks Rebecca for the report and Mark for the analysis of the problem.
This should be fixed in -r342290.
Kirk McKusick
=-=-=
From:Kirk McKusick
Date:Fri, 21 Dec 2018 01:09:25 + (UTC)
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn-src-h
ubscr...@freebsd.org"
You can browse the history at http://svnweb.freebsd.org/csrg/
The repository is also available via FTP:
ftp://ftp.freebsd.org/pub/FreeBSD/development/CSRG/csrg_svn.tbz
Hope this helps,
Kirk McKusick
___
freebsd-c
ince 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
Both stable-11 and stable-12 clear the "use hashes" flags. If the disk
is moved back to a 13-head system they remain disabled until reenabled
by running fsck in interactive mode and requestin
eck hash addition request.
Filesystems created on 13 will get superblock check hashs. But if you
boot a 13 filesystem using a 12-stable kernel, they will be disabled and
left disabled even if you boot the filesystem on 13 again.
Thanks for pointing out the error on the fsck_ufs manual page. The first
cify using `umount -F', but
regretably -F is already in use to specify an alternate fstab file).
A very forcible unmount says to simply abandon dirty buffers that
it cannot write. In the event of a disk dying, that would be all
of the dirty buffers.
Kirk McKusick
__
try:
>
> diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c
> index ff37de8..0ad6ef7 100644
> --- a/sys/kern/vfs_subr.c
> +++ b/sys/kern/vfs_subr.c
> @@ -2783,6 +2783,7 @@ _vdrop(struct vnode *vp, bool locked)
> vp->v_op = NULL;
> #endif
> bzero(&
it would at first
appear to be. Thank-you for your efforts to date and I look
forward to the transition (hopefully in the 11.1 release) as
I believe it will be a huge step forward.
Kirk McKusick
___
freebsd-current@freebsd.org mailing list
https
Thanks for all your work on this project. As I still use roff for
our book and for many of my presentations, it is a topic of interest
to me. That said, I am fine with roff dropping out of base as I can
easily enough bring it in from ports. And I am curious to try using
heirloom doctools on our boo
been no changes to the code that manage the filesystem bitmaps
in decades (nearly three decades), so a software cause of this panic is
unlikely to have been recently introduced. Hence, I would not spend a lot
of time trying to get a backtrace, etc.
Kirk McKusick
_
increase the KVM
allocated to the buffer cache.
Kirk McKusick
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
you wish to go back to using SU+J after the test, you can
reenable SU+J by running:
umount
tunefs -j enable
mount
When responding to me, it is best to use my
email as I tend to read it more regularly.
Kirk McKusick
___
snapshot is active on a filesystem
DOES NOT WORK. It leaves your filesystem with duplicate blocks that can
only be removed by manually running fsck and correcting the duplicate
block entries by hand. If you need to use snapshots, then run with SU
and not SU+J. When journal rollback properly handl
> Date: Sun, 24 Feb 2013 22:41:21 +0300
> Subject: Re: [PATCH] Fix sbin/fsdb/fsdbutil.c for r247212
> From: Sergey Kandaurov
> To: David Wolfskill
> Cc: curr...@freebsd.org, Kirk McKusick
>
> On 24 February 2013 19:25, David Wolfskill wrote:
>> On Sun, Feb 24, 2013
I pointed Robert and Pawel at your discussion on creating a new
PRIV_KMEM and adding a check for it in memopen(). I am of the opinion
that this is a good idea, but I am hoping that one of Robert or Pawel
will comment since they are much more active in this area.
Kirk McKusick
> Date: Sat, 15 Jun 2013 17:23:50 -0600
> From: Jamie Gritton
> To: FreeBSD Current
> CC: Kirk McKusick ,
> Konstantin Belousov ,
> Alexander Leidinger ,
> Pawel Jakub Dawidek ,
> Robert Watson
> Subject: Re: A PRIV_* flag for /dev/
> Date: Tue, 9 Jul 2013 18:29:01 -0700
> Subject: Re: Kernel crash during heavy disk access
> From: Adrian Chadd
> To: Benjamin Kaduk , Jeff Roberson ,
> Kirk McKusick
> Cc: Eric Camachat , curr...@freebsd.org
>
> Well, best to tell kirk and jeffr.
>
> Je
> Date: Tue, 3 May 2011 22:40:26 -0700
> Subject: Nasty non-recursive lockmgr panic on softdep only enabled UFS
> partition when filesystem full
> From: Garrett Cooper
> To: Jeff Roberson ,
> Marshall Kirk McKusick
> Cc: FreeBSD Current
>
> Hi Jeff and D
renamed to MNT_NULL_CACHE, added to MNT_VISFLAGMASK,
and listed in MNTOPT_NAMES. It probably belongs in the set
described as `Flags set by internal operations, but visible
to the user.' With this change, it will be displayed by
the mount command and show up in the statfs flags.
> Date: Sun, 10 Mar 2024 19:21:54 +0200
> From: Konstantin Belousov
> To: Kirk McKusick
> Cc: curr...@freebsd.org
> Subject: Re: Reason why "nocache" option is not displayed in "mount"?
>
> On Sun, Mar 10, 2024 at 01:53:05AM +, Kirk McKusick wrote:
ext, mkimg(1) is used to feed the resultant md(4)-based .img
> filesystem (after umount(8)) to create the final output image.
>
> Glen
Glen,
Can you try running fsck on the md(4) disk after you do the unmount to
see if it finds any problems (`fsck /dev/md0')? If that comes up clean
(as it should), then I can investigate what it is about mkimg that causes
problems. If fsck finds problems, then there is an issue in the base UFS
infrastructure.
Kirk McKusick
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
AL.
> I answered Y.
> FWIW the systems are UFS2 (ffs) have gpart labels, and were newfs'd thusly:
> newfs -U -j
>
> Thank you for all your time, and consideration.
>
> --Chris
This problem should have been fixed with this commit:
r328914 | mckusick |
ics let you see how much of a backlog
of BIO_DELETEs you have backed up at/in the disk drive and you can track
how quickly they drain.
Kirk McKusick
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
T
From: Kirk McKusick
To: FreeBSD Current ,
FreeBSD Filesystems
Subject: CFT: TRIM Consolodation on UFS/FFS filesystems
Date: Mon, 20 Aug 2018 12:40:56 -0700
Oops, forgot that attachments get stripped. Below are the diffs for
gathering statistics. Sorry to those of you on Gmail for whom
torage of data on two physically separated machines
> connected over a TCP/IP network.
> Only one machine (cluster node) can actively use storage provided by
> .Nm .
>
> --
> Steve
Fixed in -r355995, thanks.
Kirk McKusick
_
1 - 100 of 104 matches
Mail list logo
