[Bug 204997] experienced multiple processes in suspfs with complete blackout of the filesystem

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

Mark Linimon <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|freebsd-***@FreeBSD.org |freebsd-***@FreeBSD.org
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

Kirk McKusick <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org

--- Comment #1 from Kirk McKusick <***@FreeBSD.org> ---
Which filesystem was the one that hung?

Assuming you know, if the problem happens again try disabling journaled
soft-updates on that filesystem to see if that feature is what is causing your
problem. Specifically run this command on the unmounted filesystem:

tunefs -j disable /<fs>

where <fs> is the filesystem to be disabled (such as /data, /l, etc).
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

--- Comment #2 from Polina Soloviova <***@in.spb.ru> ---
(In reply to Kirk McKusick from comment #1)

Hi!
It was /1 mount point

Thank you for your comment. We now monitoring server's processes in state
suspfs, and will send a feedback as soon as it happens again.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

Miroslav Lachman <***@quip.cz> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@quip.cz

--- Comment #3 from Miroslav Lachman <***@quip.cz> ---
Just for the record. I experienced this problem 11 days ago. Some processes
(rsync, sshd, proftpd, httpd) where stucked at suspfs state, unkillable and
system cannot be rebooted (infinite waiting after All buffers synced).
The problem appeared again today. I disabled journaling. We'll see if it helped
or not.

FreeBSD 10.4-RELEASE-p9 amd64 GENERIC

FS was originally mounted as:
/dev/da1p1 on /vol0 (ufs, local, noatime, nosuid, journaled soft-updates)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

--- Comment #4 from Kirk McKusick <***@FreeBSD.org> ---
(In reply to Miroslav Lachman from comment #3)
Did disabling journaling make the problem go away?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

--- Comment #5 from Miroslav Lachman <***@quip.cz> ---
(In reply to Kirk McKusick from comment #4)
There were 2 weeks between suspfs occurences so I will wait a few weeks and
then let you know if it helps or not. (so far so good, no suspfs problem in
last 5 days)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204997

Mark Linimon <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|New |Closed
Resolution|--- |Overcome By Events
Assignee|***@FreeBSD.org |***@FreeBSD.org

--- Comment #6 from Mark Linimon <***@FreeBSD.org> ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.