Re: premature umount

2021-08-26 Thread Geoffrey Leach
On Thu, 26 Aug 2021 10:56:47 -0700 Samuel Sieb wrote: > On 2021-08-26 10:34 a.m., Roberto Ragusa wrote: > > On 8/26/21 2:57 PM, Geoffrey Leach wrote: > >> On Thu, 26 Aug 2021 09:11:34 +0200 > >> Roberto Ragusa wrote: > >> > >>> On 8/26/21 7:01 AM, Geoffrey Leach wrote: > On Wed, 25 Au

Re: premature umount

2021-08-26 Thread Geoffrey Leach
On Thu, 26 Aug 2021 10:48:15 -0700 Gordon Messmer wrote: > On 8/25/21 9:26 PM, Samuel Sieb wrote: > > You could add a "sync" after the copy and before the "umount". > > > https://utcc.utoronto.ca/~cks/space/blog/unix/TheLegendOfSync > > We're getting into myths and legends territory.  Runni

Re: premature umount

2021-08-26 Thread Samuel Sieb
On 2021-08-26 10:34 a.m., Roberto Ragusa wrote: On 8/26/21 2:57 PM, Geoffrey Leach wrote: On Thu, 26 Aug 2021 09:11:34 +0200 Roberto Ragusa wrote: On 8/26/21 7:01 AM, Geoffrey Leach wrote: On Wed, 25 Aug 2021 21:26:19 -0700 You could add a "sync" after the copy and before the "umount".

Re: premature umount

2021-08-26 Thread Samuel Sieb
On 2021-08-26 10:48 a.m., Gordon Messmer wrote: On 8/25/21 9:26 PM, Samuel Sieb wrote: You could add a "sync" after the copy and before the "umount". https://utcc.utoronto.ca/~cks/space/blog/unix/TheLegendOfSync We're getting into myths and legends territory.  Running sync before umount isn

Re: premature umount

2021-08-26 Thread Gordon Messmer
On 8/25/21 9:26 PM, Samuel Sieb wrote: You could add a "sync" after the copy and before the "umount". https://utcc.utoronto.ca/~cks/space/blog/unix/TheLegendOfSync We're getting into myths and legends territory.  Running sync before umount isn't harmful, but umount will flush any dirty buffe

Re: premature umount

2021-08-26 Thread Geoffrey Leach
On Thu, 26 Aug 2021 19:34:55 +0200 Roberto Ragusa wrote: > On 8/26/21 2:57 PM, Geoffrey Leach wrote: > > On Thu, 26 Aug 2021 09:11:34 +0200 > > Roberto Ragusa wrote: > > > >> On 8/26/21 7:01 AM, Geoffrey Leach wrote: > >>> On Wed, 25 Aug 2021 21:26:19 -0700 > >> > You could add a "

Re: premature umount

2021-08-26 Thread Roberto Ragusa
On 8/26/21 2:57 PM, Geoffrey Leach wrote: On Thu, 26 Aug 2021 09:11:34 +0200 Roberto Ragusa wrote: On 8/26/21 7:01 AM, Geoffrey Leach wrote: On Wed, 25 Aug 2021 21:26:19 -0700 You could add a "sync" after the copy and before the "umount". Just what I needed. Thanks. Absolutely not. If

Re: premature umount

2021-08-26 Thread John Westerdale
The rsync wouldn't fix anything, but copy/copy would -at best- overwrite the same data ... rsync would compare and update if different. Either case, purely a workaround. Umount of a file system should include a sync (for open files on that file system). John Westerdale Sr Container Consultant

Re: premature umount

2021-08-26 Thread Geoffrey Leach
On Thu, 26 Aug 2021 09:09:30 -0400 John Westerdale wrote: > maybe ... rsync... rsync ... sync ... unmount? > > > On Thu, Aug 26, 2021 at 9:01 AM Geoffrey Leach > wrote: > > > On Thu, 26 Aug 2021 19:20:06 +0930 > > Tim via users wrote: > > > > > On Wed, 2021-08-25 at 21:21 -0700, Geoffrey L

Re: premature umount

2021-08-26 Thread John Westerdale
maybe ... rsync... rsync ... sync ... unmount? John Westerdale Sr Container Consultant * RHCSA-8.2* Red Hat NYC Office/WFH john.westerd...@redhat.com M: 201-376-9993 IM: jwesterd He / Him / His I respect your Life-Work balance. No nee

Re: premature umount

2021-08-26 Thread Geoffrey Leach
On Thu, 26 Aug 2021 19:20:06 +0930 Tim via users wrote: > On Wed, 2021-08-25 at 21:21 -0700, Geoffrey Leach wrote: > > I have a script that mounts an MP3 device, copies files and umounts. > > As I have counted on the umount to hang until the data transfer is > > complete. That has worked fine unt

Re: premature umount

2021-08-26 Thread Geoffrey Leach
On Thu, 26 Aug 2021 09:11:34 +0200 Roberto Ragusa wrote: > On 8/26/21 7:01 AM, Geoffrey Leach wrote: > > On Wed, 25 Aug 2021 21:26:19 -0700 > > >> You could add a "sync" after the copy and before the "umount". > > > > Just what I needed. Thanks. > > Absolutely not. > If umount is failing

Re: premature umount

2021-08-26 Thread Tim via users
On Wed, 2021-08-25 at 21:21 -0700, Geoffrey Leach wrote: > I have a script that mounts an MP3 device, copies files and umounts. > As I have counted on the umount to hang until the data transfer is > complete. That has worked fine until recently. Now the umount > finishes, leaving much of the data u

Re: premature umount

2021-08-26 Thread Joe Zeff
On 8/26/21 1:11 AM, Roberto Ragusa wrote: If umount is failing to do a complete flushing by itself it is a serious (press-release level) bug and must be investigated. I agree that an issue like this needs to be reported and investigated, but there's no reason not to use such a simple mitigatio

Re: premature umount

2021-08-26 Thread Roberto Ragusa
On 8/26/21 7:01 AM, Geoffrey Leach wrote: On Wed, 25 Aug 2021 21:26:19 -0700 You could add a "sync" after the copy and before the "umount". Just what I needed. Thanks. Absolutely not. If umount is failing to do a complete flushing by itself it is a serious (press-release level) bug and mus

Re: premature umount

2021-08-25 Thread Geoffrey Leach
On Wed, 25 Aug 2021 21:26:19 -0700 Samuel Sieb wrote: > On 8/25/21 9:21 PM, Geoffrey Leach wrote: > > I have a script that mounts an MP3 device, copies files and > > umounts. As I have counted on the umount to hang until the data > > transfer is complete. That has worked fine until recently. Now

Re: premature umount

2021-08-25 Thread Samuel Sieb
On 8/25/21 9:21 PM, Geoffrey Leach wrote: I have a script that mounts an MP3 device, copies files and umounts. As I have counted on the umount to hang until the data transfer is complete. That has worked fine until recently. Now the umount finishes, leaving much of the data uncopied. You're say

premature umount

2021-08-25 Thread Geoffrey Leach
I have a script that mounts an MP3 device, copies files and umounts. As I have counted on the umount to hang until the data transfer is complete. That has worked fine until recently. Now the umount finishes, leaving much of the data uncopied. Fedora 32, up-to-date at end-of-life. Has some paramet