lkml.org 
[lkml]   [2003]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem?
    Andy Pfiffer <andyp@osdl.org> wrote:
    >
    > So now the important question: is it wrong to not sync_blockdev() until
    > the count drops to 0?

    Should be OK. The close will not sync anything if someone else has the
    blockdev open (ie: there's a filesystem mounted there).

    But sync() should certainly write everything out, and lilo does perform a
    sync.

    I'd be interested in seeing the contents of /proc/meminfo immediately after
    the lilo run, see if there's any dirty memory left around.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:36    [W:0.021 / U:58.872 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site