On Wed, Mar 20, 2024 at 10:17:23AM +, Ice Cream wrote:
> Hi, when I try to run `mount_full /root/xyz/a /root/xyz/b`
> I get the following error:
> `mount_full: /root/xyz/a on /root/xyz/b: Operation
> not supported by device`
> Any tips for debugging this?
Does your kernel have
file-sy
> Hi, when I try to run `mount_full /root/xyz/a /root/xyz/b`
> I get the following error:
> `mount_full: /root/xyz/a on /root/xyz/b: Operation
> not supported by device`
> Any tips for debugging this?
Add printfs in the kernel codepaths? That's what I'd start with.
(Well, actually, I'd start by r
> Martin Husemann writes:
> On Wed, Mar 20, 2024 at 05:32:10AM +, Mathew, Cherry G.* wrote:
>> I look forward to your comments and test results, if any.
> I think moving heartbeat() to a callout context voids it's
> purpose.
Thanks, Martin.
Please find attached an updat
Hi, when I try to run `mount_full /root/xyz/a /root/xyz/b`
I get the following error:
`mount_full: /root/xyz/a on /root/xyz/b: Operation
not supported by device`
Any tips for debugging this?
I implemented mount_full by copying the nullfs
file system and then adding `full_write()`
in full_vnops.c t
On Wed, Mar 20, 2024 at 05:32:10AM +, Mathew, Cherry G.* wrote:
> I look forward to your comments and test results, if any.
I think moving heartbeat() to a callout context voids it's purpose.
Martin
Hello,
I'm investigating how to make our kernel less reliant on hardclock(9)
being called at hz(9).
Please find attached a patch to reduce hardclock(9)'s responsibilities
wrt the rest of the system timekeeping.
The idea is that hardclock(9) will drive callout_hardclock() for now,
until we modify
