From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4AE97C433E0 for ; Thu, 9 Jul 2020 13:54:23 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 034DD20708 for ; Thu, 9 Jul 2020 13:54:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="PMXuJHEe" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 034DD20708 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1jtWzA-0001ZI-LF; Thu, 09 Jul 2020 09:53:12 -0400 Received: from mail-ej1-x62a.google.com ([2a00:1450:4864:20::62a]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1jtWz6-0001Z4-1m for kernelnewbies@kernelnewbies.org; Thu, 09 Jul 2020 09:53:08 -0400 Received: by mail-ej1-x62a.google.com with SMTP id l12so2324120ejn.10 for ; Thu, 09 Jul 2020 06:53:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=iQ04KR8lJXl6azkTMR6yCa/Wnp08oHoxJzQxWs/cbqY=; b=PMXuJHEeYoK5PbhWALz+rSE9Z3eYTQ8P6NSK8kgsCIU+nkQBhz9mzo8A8oQcDhBGXY HZjBlUc1yh1EJs9IBW8Ni71pn/1sgn2SOS4yWu1IA4i2CPs+9nH/j21Ht6Qix5Cmbz2i WhaK5XNuGGPOIRjvzZhVc0xRiNrik5OOddXO85iImvDPsOTMyUlxP01BxejXAhxhe9JC ht8dZGnPSM+ZWi7sLjUXFwoMZr+OcPwruCAcvvmN+g1w2cfMpD5ED5e/6u33jQM+SM1m hMG2Z2wkJFvNZTMhHpI/rexXQZ+cA/hhIlf712295Pk2EQWSry1RaM81Vw8AL3rAQJ6D l3wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=iQ04KR8lJXl6azkTMR6yCa/Wnp08oHoxJzQxWs/cbqY=; b=JE1K9IlJm90xt4l+34838ErHTRWMFn1TMK+IcaJKCougJq/sbdBwjbCXO7GJ5PyvLZ 30r7CYY+hc99p/f5cnCAerAAQccLihPli9BUT7reJhPpWvxngyM90PFLJYw7GyhZTMhx fgqCFwRLkAyZ/WjDbYIit/w2+adt3CrEckKUfGz7AmsiP92Yiu0z4nMHPwT3/R8xaOWS Fy6XnDGYK6Wak6Qiq1ivjliA34gwm9bo7qSUugH5Gi7YvnM+gWzmnnpRkLC9q2YgxyId si1hRI+NYAKJNbRQy6KJimFVzhM6qnKH/4//hfydZoeW9v4St/j+s6DZrMsujgTXX0v8 XmEw== X-Gm-Message-State: AOAM532nnDMu/TjbyHOkUuO2G/4Rux9uLWEzOh+JKAyTCiP+KEmxTgXT aNBoIEBsYJirvl73XsC0okOrhaqb28b1T0r+X+g= X-Google-Smtp-Source: ABdhPJyeq85d27J472qPXW782RbPqMA+boywvu7rKIoab7qVllLVsl9hQc+049PDV4LrQ17PltGwx3LHHbcRSP1vSFU= X-Received: by 2002:a17:906:cc0e:: with SMTP id ml14mr55215049ejb.432.1594302725316; Thu, 09 Jul 2020 06:52:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Abu Rasheda Date: Thu, 9 Jul 2020 06:51:29 -0700 Message-ID: Subject: Re: how to debug problem with "failing unmounting" To: Tomek The Messenger , Linux Kernel List X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8987488766506913551==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============8987488766506913551== Content-Type: multipart/alternative; boundary="0000000000009b64c105aa0287c4" --0000000000009b64c105aa0287c4 Content-Type: text/plain; charset="UTF-8" On Thu, Jul 9, 2020 at 5:24 AM Tomek The Messenger < tomekthemessenger@gmail.com> wrote: > Hi > On the soc on which I work there is issue with unmouting some > partitions/directories during /sbin/reboot, here is some example: > > [ OK ] Stopped target Local File System. > Unmouting Temporary Directory (/tmp)... > Unmouting /run/user/0... > ... > [ FAILED ] Failed unmouting Temporary Directory (/tmp). > [ FAILED ] Failed unmouting /run/user/0. > .... > > Unfortunately like it is typical in kernel information about why > unmouting failed doesn't appear. So seems like searching in darkness what > is going on. Is any way how to search in darkness? Firstly I should make > sure /tmp or /run/user/0 is really a partition and was mount at linux > startup. Then maybe I should check access rights if it is rwx. What else > can be tried here? > _______________________________________________ > > make sure there is no process which has these directories open (cd into it or open a file), you can I put some printk in the code to debug what leads to this condition. --0000000000009b64c105aa0287c4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Jul 9, 2020 at 5:24 AM Tomek = The Messenger <tomektheme= ssenger@gmail.com> wrote:
Hi
On the soc on which I work there i= s issue with unmouting some partitions/directories during /sbin/reboot, her= e is some example:

[=C2=A0 =C2=A0OK=C2=A0 =C2=A0]= =C2=A0 Stopped target Local File System.
Unmouting Temporary Dire= ctory (/tmp)...
Unmouting /run/user/0...=C2=A0
...<= /div>
[=C2=A0 =C2=A0FAILED=C2=A0 ]=C2=A0 Failed=C2=A0unmouting=C2=A0Tem= porary Directory (/tmp).
[=C2=A0 =C2=A0FAILED=C2=A0 ]=C2=A0 F= ailed=C2=A0unmouting=C2=A0 /run/user/0.=C2=A0
....

Unfortunatel= y=C2=A0like it is typical in kernel information=C2=A0about why unmouting=C2= =A0failed doesn't appear.=C2=A0 So seems like searching in darkness wha= t is going on. Is any way how to search in darkness? Firstly=C2=A0I should = make sure /tmp or /run/user/0 is really a partition and was mount=C2=A0at l= inux startup. Then maybe I should check access rights if it is rwx. What el= se can be tried here?
_______________________________________________

ma= ke sure there is no process which has these directories open (cd into it or= open a file), you can I put some printk in the code to debug what leads to= this condition.=C2=A0
--0000000000009b64c105aa0287c4-- --===============8987488766506913551== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============8987488766506913551==--