Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why would someone use JFS rather than raw disk access for a database application?

application database disk JFS raw
0
Posted

Why would someone use JFS rather than raw disk access for a database application?

0

The real issue here is from a performance standpoint, do you want raw or filesystem access? JFS adds another layer to the I/O path. JFS is going to be slower than raw I/O. Yes, JFS has a log, but that is a log for the file system’s structure. The database would still need to be recovered after the fsck of JFS completed. With LVM, you can use raw I/O. A LV does not need to have a file system on it. So, you can do all the usual striping and mirroring with LVM and still have raw I/O (the database opens /dev/vgXX/rlvolX). However, there are many reasons customers use file systems. Namely, backup is a lot easier with file systems. Also, JFS’s online backup is great. Finally, many people like seeing their data (via bdf, etc).

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123