Lennart Poettering writes:
> Is it? I do that all the time? It's news to me that this wasn't a good
> idea...
It is terribly slow because it copies all of the unused data. It's also
pretty terrible for SSDs to write the entire drive. Most people use
higher level tools like parted magic or gpar
On Mi, 07.05.25 09:07, Phillip Susi (ph...@thesusis.net) wrote:
> Lennart Poettering writes:
>
> > Maybe in your case, in the general case that's not so however. People
> > often dd images to disks, and hence it's essential the partitions show
> > up once that's complete.
>
> I think you have tha
Lennart Poettering writes:
> Maybe in your case, in the general case that's not so however. People
> often dd images to disks, and hence it's essential the partitions show
> up once that's complete.
I think you have that backwards. That is, it is taken care of in the
general case, and only not
On Di, 06.05.25 13:03, Phillip Susi (ph...@thesusis.net) wrote:
> Lennart Poettering writes:
>
> > Not quite. it will issue that when a process closes the block device
> > after it was open for *write*. That's a relevant
> > distinction. Typically, userspace tools only open raw block devices
> >
Lennart Poettering writes:
> Not quite. it will issue that when a process closes the block device
> after it was open for *write*. That's a relevant
> distinction. Typically, userspace tools only open raw block devices
> only to partition/format file systems for write, and thus if we then
> rerea
On Di, 06.05.25 15:47, Lennart Poettering (lenn...@poettering.net) wrote:
> This is not new behaviour btw. It's widely documented (as above), and
> has been that way for decades.
(One more note: you can also disable the inotify thing if you like via
OPTIONS and "watch" in the udev rules file. But
On Do, 10.04.25 12:47, Phillip Susi (ph...@thesusis.net) wrote:
> It appears that udev calls BLKRRPRT on a block device whenever it gets
> an inotify event that some other process has closed an fd to it.
Not quite. it will issue that when a process closes the block device
after it was open for *w
Nobody has any thoughts on this behavior that to me at least, appears to
be a bug?
Phillip Susi writes:
> It appears that udev calls BLKRRPRT on a block device whenever it gets
> an inotify event that some other process has closed an fd to it. This
> causes all of the partitions on the disk to
