Date: Mon, 24 Apr 2006 16:28:59 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: fsck_ufs locked in snaplk Message-ID: <20060424202859.GA18457@xor.obsecurity.org> In-Reply-To: <20060425001751.S44618@woozle.rinet.ru> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org> <20060424091803.L20593@woozle.rinet.ru> <20060424215650.P36233@woozle.rinet.ru> <20060424181531.GA13774@xor.obsecurity.org> <20060425001751.S44618@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 25, 2006 at 12:24:07AM +0400, Dmitry Morozovsky wrote: > On Mon, 24 Apr 2006, Kris Kennaway wrote: >=20 > KK> > What bothers me most is that it is the only machine reproducibly ha= ngs in=20 > KK> > snapshots, and it did not hang before RELENG_5 -> RELENG_6 upgrade.= Other=20 > KK> > RELENG_6 machines do snapshot backups flawlessly (knock-on-wood!) > KK>=20 > KK> Are you quite certain it's running up-to-date RELENG_6_1? All known > KK> snapshot deadlock issues were believed to have been fixed a few weeks > KK> ago. If so, we might need you to enable extra debugging to track this > KK> down. >=20 > Yes, I'm sure it's recent RELENG_6_1: >=20 > marck@office:/usr/src> cvs stat sys/ufs/ffs/ffs_snapshot.c=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > File: ffs_snapshot.c Status: Up-to-date >=20 > Working revision: 1.103.2.5 > Repository revision: 1.103.2.5 /home/ncvs/src/sys/ufs/ffs/ffs_sn= apshot.c,v > Sticky Tag: RELENG_6_1 (branch: 1.103.2.5.2) > Sticky Date: (none) > Sticky Options: (none) >=20 > marck@office:/usr/src> cvs -R up > P etc/rc.d/SERVERS > P release/doc/en_US.ISO8859-1/errata/article.sgml > P release/doc/en_US.ISO8859-1/relnotes/common/new.sgml > P release/doc/share/sgml/release.ent > P release/doc/zh_CN.GB2312/errata/article.sgml > P release/doc/zh_CN.GB2312/relnotes/common/new.sgml > P sys/amd64/amd64/identcpu.c > P sys/amd64/amd64/initcpu.c > P sys/amd64/amd64/pmap.c > P sys/amd64/include/md_var.h > P sys/amd64/include/specialreg.h > P sys/i386/i386/identcpu.c > P sys/i386/i386/initcpu.c > P sys/i386/include/md_var.h > P sys/i386/include/specialreg.h > P sys/ia64/ia64/nexus.c >=20 > (all these changes are non-relevant, are they?) Yes. > I'll try to build DDB kernel tomorrow evening to check. Which commands sh= ould I=20 > issue in ddb ? 'show lockedvnods', 'ps' and 'alltrace' are important. Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFETTUKWry0BWjoQKURAqyHAKDfv4YZ6UJdPBEKBLWrWM4e+TGixACfdc37 0Klcg/RRUwebMdh/Ggzu9xM= =sE0D -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060424202859.GA18457>