| This article is ratedStart-class on Wikipedia'scontent assessment scale. It is of interest to the followingWikiProjects: | |||||||||||
| |||||||||||
It seems that with other popular file systems it's standard to include a section detailing the criticisms or shortcomings of the system. Important for those of us also looking for a quick reference on different file systems. Can someone with experience in JFS write something up for this need?24.236.187.38 (talk)04:43, 5 December 2008 (UTC)[reply]
As far as I know is the maximum filesystem size 32TB according to its manpage and my experiences:
The maximum size is determined by the file system block size:
fs block size (byte) MAX fssize (TB) =========================================== 512 4 1024 8 2048 16 4096 32— Precedingunsigned comment added by193.201.183.198 (talk)14:23, 29 January 2014 (UTC)[reply]
Why is this article called "IBM Journaled File System 2 (JFS2)"? Nowhere in the article is "JFS2" mentioned or discussed. Nor should there be an acronym in the page title. I'd move it to "Journaled File System", but that page already exists (and redirects HERE?). What the heck?—Kbolino01:39, 4 February 2007 (UTC)[reply]
I believe it is called JFS2 only under AIX where also the ancient JFS1 file system exists (hence, there is a need to distinguish these two file systems). For other operating systems (OS/2 and Linux to name) there is only one JFS file system which is called simply "JFS" (despite that it is based on JFS2 sources from AIX). So, I would vote to drop "2" from the main article name and call it simply "Journaled File System (JFS)". The extra "(JFS)" is needed here to avoid confusion with thejournaled file system as a type of file systems. Another option is the name "JFS file system" (which sounds even better to me).Maxal00:24, 14 June 2007 (UTC)[reply]
The current nameJFS file system is really dumb. Literally we are saying "journaled file system file system" can we at least switch it toJournaled File System (IBM) orJournaled File System (UNIX). --vossman04:03, 4 August 2007 (UTC)[reply]
A JFS supports - Compressed file systemsOK for single user workstationFine for off-line backup areasOtherwise avoid - eats CPU time
http://www-941.ibm.com/collaboration/wiki/display/WikiPtype/JFS—Precedingunsigned comment added by84.58.242.213 (talk)14:01, 2 October 2007 (UTC)[reply]
Extents:
contagious space -> contigous space—Precedingunsigned comment added by81.149.223.5 (talk)15:49, 15 February 2008 (UTC)[reply]
Shouldn't we use SI units ?
"4 PB (4 × 10245 bytes)" sould be "4 PiB (4 × 10245 bytes)"
See :http://en.wikipedia.org/wiki/Octet_(computing)— Precedingunsigned comment added by91.198.30.249 (talk)12:17, 28 June 2011 (UTC)[reply]
This section is unclear, and the title is a little confusing. The section suggests I-Node allocation itself it a dynamic process which does not have a limit in the number of i-nodes allocated for a filesystem. This is false. JFS does have a hard limit for i-nodes which is defined when file system is created, and is a function of the amount of free space available. With JFS i-nodes can be added, however one must increase the available disk space and grow the file system to add additional extents. This is contrary to file systems such as ReiserFS, Reiser4, and ZFS in which i-node allocation is completely dynamic, as they are allocated when the files are created opposed to when the file system is created or expanded. With JFS is it possible (however unlikely) to utilize all the available i-nodes and still have available disk space; in contrast it is not actually possible to utilize all the i-nodes on the aforementioned file systems.
See :Working with JFS i-nodes— Precedingunsigned comment added by64.125.235.2 (talk)01:08, 10 January 2012 (UTC)[reply]
Somebody put a link and irrelevant sentence about backblaze, and linked it to their wikipedia page. I trashed it. --Ian Macintosh—Precedingundated comment added15:48, 10 January 2012 (UTC).[reply]
Hello fellow Wikipedians,
I have just modified one external link onJFS (file system). Please take a moment to reviewmy edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visitthis simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.After February 2018, "External links modified" talk page sections are no longer generated or monitored byInternetArchiveBot. No special action is required regarding these talk page notices, other thanregular verification using the archive tool instructions below. Editorshave permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see theRfC before doing mass systematic removals. This message is updated dynamically through the template{{source check}}(last update: 5 June 2024).
Cheers.—InternetArchiveBot(Report bug)21:04, 18 November 2017 (UTC)[reply]
Hello fellow Wikipedians,
I have just modified one external link onJFS (file system). Please take a moment to reviewmy edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visitthis simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.After February 2018, "External links modified" talk page sections are no longer generated or monitored byInternetArchiveBot. No special action is required regarding these talk page notices, other thanregular verification using the archive tool instructions below. Editorshave permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see theRfC before doing mass systematic removals. This message is updated dynamically through the template{{source check}}(last update: 5 June 2024).
Cheers.—InternetArchiveBot(Report bug)11:55, 5 December 2017 (UTC)[reply]