Is there a memory block device?
I know that tmpfs is a memmory filesystem. Is there a possibility to create also a memory block device? Is there a possibility to create for example a 1 GB memory block device (from the RAM)? -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Is there a memory block device?
I know that tmpfs is a memmory filesystem. Is there a possibility to create also a memory block device? Is there a possibility to create for example a 1 GB memory block device (from the RAM)? -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Is there a "blackhole" /dev/null directory?
Hello Linux Kernel Hackers, /dev/null is often very useful, specially if programs force to save data in some file. But some programs like to creates different temporary file names, so /dev/null could no more work. What is with a "/dev/null"-directory? I mean a "blackhole pseudo directory" which eats every write to null. Here is how it could work: mount -t nulldir nulldir /dev/nulldir Now if a program does a create(2), it creates in the memory the file with its fd. Then if a program does a write(2) to the fd, it eats the writes and give out fakely it has written the number of bytes. When the program calls does a close(2) of the fd, then the complete inode is deleted in the memory. The directory should be permanently empty except for the inodes with open file descriptors. So only inode information would be temporary saved in this "nulldir tmpfs" directory. Is there already existing a possibility to create a null directory? -- Best regards, Mika Lawando -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Is there a blackhole /dev/null directory?
Hello Linux Kernel Hackers, /dev/null is often very useful, specially if programs force to save data in some file. But some programs like to creates different temporary file names, so /dev/null could no more work. What is with a /dev/null-directory? I mean a blackhole pseudo directory which eats every write to null. Here is how it could work: mount -t nulldir nulldir /dev/nulldir Now if a program does a create(2), it creates in the memory the file with its fd. Then if a program does a write(2) to the fd, it eats the writes and give out fakely it has written the number of bytes. When the program calls does a close(2) of the fd, then the complete inode is deleted in the memory. The directory should be permanently empty except for the inodes with open file descriptors. So only inode information would be temporary saved in this nulldir tmpfs directory. Is there already existing a possibility to create a null directory? -- Best regards, Mika Lawando -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help debugging filesystem activity?
Guillaume Chazarain schrieb: On Feb 11, 2008 2:17 PM, rzryyvzy <[EMAIL PROTECTED]> wrote: $ cat /proc/fs/vfs/reading_files $ cat /proc/fs/vfs/writing_files You can try: # echo 1 > /proc/sys/vm/block_dump # dmesg Thanks, it works. This option rocks. I did not know about that. This is what I really like in Linux: Everything is possible. -- Best regards, Mika Lawando -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Help debugging filesystem activity?
My hard disk on my server is all the time readding and writing some files (I can see it with dstat). However I would like to know which files exactly are readden or written all the time. I know that each filesystem activity goes by the VFS (virtual filesystem). Is it possible to see all current open files in the VFS? For example with a command like: $ cat /proc/fs/vfs/open_files $ cat /proc/fs/vfs/reading_files $ cat /proc/fs/vfs/writing_files ? Is there a possibility? It should be on the VFS level to be independent of the used filesystem. -- Best regards -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help debugging filesystem activity?
Guillaume Chazarain schrieb: On Feb 11, 2008 2:17 PM, rzryyvzy [EMAIL PROTECTED] wrote: $ cat /proc/fs/vfs/reading_files $ cat /proc/fs/vfs/writing_files You can try: # echo 1 /proc/sys/vm/block_dump # dmesg Thanks, it works. This option rocks. I did not know about that. This is what I really like in Linux: Everything is possible. -- Best regards, Mika Lawando -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Help debugging filesystem activity?
My hard disk on my server is all the time readding and writing some files (I can see it with dstat). However I would like to know which files exactly are readden or written all the time. I know that each filesystem activity goes by the VFS (virtual filesystem). Is it possible to see all current open files in the VFS? For example with a command like: $ cat /proc/fs/vfs/open_files $ cat /proc/fs/vfs/reading_files $ cat /proc/fs/vfs/writing_files ? Is there a possibility? It should be on the VFS level to be independent of the used filesystem. -- Best regards -- E-Mail sent with anti-spam site TrashMail.net! Free disposable email addresses: http://www.trashmail.net/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: What is the limit size of tmpfs /dev/shm ?
Tomasz Chmielewski schrieb: Hello Kernel Users, is there a size limit for tmpfs for the /dev/shm filesystem? Normally its default size is set to 2 GB. Is it possible to create a 2 TB (Terrabyte) filesystem with tmpfs? Or is there a maximum size defined in the linux kernel? Depends on your arch. I have a 64 Bits architecture (amd64/x86_64). If you're 64 bit, you need to have really loads of storage and/or RAM to accumulate 16EB: # mount -t tmpfs -o size=171798691839G tmpfs /mnt/2 # df -h (...) tmpfs 16E 0 16E 0% /mnt/2 Nice, I will try this out. I have not the money for 16E of memory of RAM! :-) lol Already to provide 1 TB it would cost at least for the memory about 20 000 EUR + the server costs which support this. -- Best regards -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: What is the limit size of tmpfs /dev/shm ?
Tomasz Chmielewski schrieb: Hello Kernel Users, is there a size limit for tmpfs for the /dev/shm filesystem? Normally its default size is set to 2 GB. Is it possible to create a 2 TB (Terrabyte) filesystem with tmpfs? Or is there a maximum size defined in the linux kernel? Depends on your arch. I have a 64 Bits architecture (amd64/x86_64). If you're 64 bit, you need to have really loads of storage and/or RAM to accumulate 16EB: # mount -t tmpfs -o size=171798691839G tmpfs /mnt/2 # df -h (...) tmpfs 16E 0 16E 0% /mnt/2 Nice, I will try this out. I have not the money for 16E of memory of RAM! :-) lol Already to provide 1 TB it would cost at least for the memory about 20 000 EUR + the server costs which support this. -- Best regards -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
