Re: Beagle and logging inotify events

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Jon Smirl" <jonsmirl@xxxxxxxxx> writes:

> On 11/14/07, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote:
>> On Nov 13, 2007, at 7:04 PM, Jon Smirl wrote:
>> > Is it feasible to do something like this in the linux file system
>> > architecture?
>> >
>> > Beagle beats on my disk for an hour when I reboot. Of course I don't
>> > like that and I shut Beagle off.
>>
>> Leopard, by the way, does exactly this: it has a daemon that starts
>> at boot time and taps FSEvents then journals file system changes to a
>> well-known file on local disk.
>
> Logging file systems have all of the needed info.

Actually most journaling file systems in Linux use block logging and
it would be probably hard to get specific file names out of a random
collection of logged blocks. And even if you could they would
hit a lot of false positives since everything is rounded up
to block level.

With intent logging like in XFS/JFS it would be easier, but even
then costly :- e.g. they might log changes to the inode but
there is no back pointer to the file name short of searching the
whole directory tree.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux