raf,
On 2020-09-14 10:07, raf via rsync wrote:
On Fri, Sep 11, 2020 at 10:53:14AM +1000, Philip Rhoades via rsync
wrote:
Roland,
On 2020-09-10 21:27, Roland wrote:
> > with rsync hanging - after breakout on /home for writing I then get:
> > "Read-only file system"
>
> if your filesystem
On Fri, Sep 11, 2020 at 10:53:14AM +1000, Philip Rhoades via rsync
wrote:
> Roland,
>
>
> On 2020-09-10 21:27, Roland wrote:
> > > with rsync hanging - after breakout on /home for writing I then get:
> > > "Read-only file system"
> >
> > if your filesystem switches to read-only, you have a
Roland,
On 2020-09-10 21:27, Roland wrote:
with rsync hanging - after breakout on /home for writing I then get:
"Read-only file system"
if your filesystem switches to read-only, you have a serious problem
with your system/storage, not with rsync.
rsync (or the workload) is simply triggering
>with rsync hanging - after breakout on /home for writing I then get:
>"Read-only file system"
if your filesystem switches to read-only, you have a serious problem
with your system/storage, not with rsync.
rsync (or the workload) is simply triggering the problem.
regards
roland
Am 10.09.20
People,
When I did:
rsync -av /home/ /mntb5/ # about 4TB
I got errors like:
'rsync [sender] expand file_list pointer array to xxx bytes, "did
move"'
with rsync hanging - after breakout on /home for writing I then get:
"Read-only file system"
So after unmounting and remounting
