1 |
DENIED
|
ROLE_USER
|
null |
|
Show voter details
|
2 |
DENIED
|
moderate
|
App\Entity\EntryComment {#1369
+user: Proxies\__CG__\App\Entity\User {#1370 …}
+entry: App\Entity\Entry {#1832 …}
+magazine: App\Entity\Magazine {#313
+icon: Proxies\__CG__\App\Entity\Image {#294 …}
+name: "linux@lemmy.ml"
+title: "linux"
+description: """
From Wikipedia, the free encyclopedia\n
\n
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).\n
\n
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.\n
\n
### Rules\n
\n
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.\n
- No misinformation\n
- No NSFW content\n
- No hate speech, bigotry, etc\n
\n
### Related Communities\n
\n
- [!opensource@lemmy.ml](https://lemmy.ml/c/opensource)\n
- [!libre_culture@lemmy.ml](https://lemmy.ml/c/libre_culture)\n
- [!technology@lemmy.ml](https://lemmy.ml/c/technology)\n
- [!libre_hardware@lemmy.ml](https://lemmy.ml/c/libre_hardware)\n
\n
Community icon by [Alpár-Etele Méder](https://www.iconfinder.com/pocike), licensed under [CC BY 3.0](https://creativecommons.org/licenses/by/3.0/)
"""
+rules: null
+subscriptionsCount: 1
+entryCount: 1406
+entryCommentCount: 28632
+postCount: 6
+postCommentCount: 214
+isAdult: false
+customCss: null
+lastActive: DateTime @1729583542 {#323
date: 2024-10-22 09:52:22.0 +02:00
}
+markedForDeletionAt: null
+tags: null
+moderators: Doctrine\ORM\PersistentCollection {#285 …}
+ownershipRequests: Doctrine\ORM\PersistentCollection {#281 …}
+moderatorRequests: Doctrine\ORM\PersistentCollection {#270 …}
+entries: Doctrine\ORM\PersistentCollection {#228 …}
+posts: Doctrine\ORM\PersistentCollection {#186 …}
+subscriptions: Doctrine\ORM\PersistentCollection {#248 …}
+bans: Doctrine\ORM\PersistentCollection {#165 …}
+reports: Doctrine\ORM\PersistentCollection {#151 …}
+badges: Doctrine\ORM\PersistentCollection {#129 …}
+logs: Doctrine\ORM\PersistentCollection {#119 …}
+awards: Doctrine\ORM\PersistentCollection {#108 …}
+categories: Doctrine\ORM\PersistentCollection {#95 …}
-id: 73
+apId: "linux@lemmy.ml"
+apProfileId: "https://lemmy.ml/c/linux"
+apPublicUrl: "https://lemmy.ml/c/linux"
+apFollowersUrl: "https://lemmy.ml/c/linux/followers"
+apInboxUrl: "https://lemmy.ml/inbox"
+apDomain: "lemmy.ml"
+apPreferredUsername: "linux"
+apDiscoverable: true
+apManuallyApprovesFollowers: null
+privateKey: null
+publicKey: null
+apFetchedAt: DateTime @1729583596 {#317
date: 2024-10-22 09:53:16.0 +02:00
}
+apDeletedAt: null
+apTimeoutAt: null
+visibility: "visible "
+createdAt: DateTimeImmutable @1698929468 {#316
date: 2023-11-02 13:51:08.0 +01:00
}
}
+image: null
+parent: Proxies\__CG__\App\Entity\EntryComment {#2451 …}
+root: Proxies\__CG__\App\Entity\EntryComment {#2356 …}
+body: """
Foreground targets are where writes initially go. Data is moved from foreground to background targets while idle or as needed. Data which is read from the background targets is moved to promote targets.\n
\n
If you set your NVMe as a promote target, SSD as foreground and your HDDs as background targets, all writes would first go to your SSD, then get copied to your HDD during idle, and finally the copy of the data on your SSD will then be marked as a cached copy. In case your SSD becomes full, then it’ll store the data on other drives. As for the promote targets, any time you read data from either the SSD or HDD that wasn’t on the NVMe, it would get cached to it, so the next read will be faster.\n
\n
The main point of the foreground vs promote is to prioritize write vs read speeds. If you value faster writes, then set your NVMe as foreground. If you value faster reads, then set your NVMe as promote. Of course, you can also set your NVMe as *both* foreground and promote to benefit from both faster reads and writes.\n
\n
But since you plan to introduce an SSD in the mix, you can create a single group for your NVMe + SSD, and a second group for the HDDs, and set your SSD group to foreground + promote, which will simplify things.\n
\n
The [Arch wiki](https://wiki.archlinux.org/title/Bcachefs) illustrates this well:\n
\n
> A recommended configuration is to use an ssd group for the foreground and promote, and an hdd group for the background (a writeback cache).\n
\n
Modified example to your scenario:\n
\n
```\n
\n
<span style="color:#323232;"># bcachefs format \n
</span><span style="color:#323232;"> --label=ssd.nvme1 /dev/nvme0n1 \n
</span><span style="color:#323232;"> --label=ssd.ssd1 /dev/sda \n
</span><span style="color:#323232;"> --label=hdd.hdd1 /dev/sdb \n
</span><span style="color:#323232;"> --label=hdd.hdd2 /dev/sdc \n
</span><span style="color:#323232;"> --replicas=2 \n
</span><span style="color:#323232;"> --foreground_target=ssd \n
</span><span style="color:#323232;"> --promote_target=ssd \n
</span><span style="color:#323232;"> --background_target=hdd \n
</span>\n
```\n
\n
If you’re concerned about chucking both the SSD and NVMe in the same group, no need to worry cause bcachefs will automatically prioritize reads from drives with lower latency as mentioned in the wiki.\n
\n
> If they are different speeds, reads for replicated data will be sent to the ones with the lowest IO latency.\n
\n
But regardless of which setup you go for, main thing to remember is to use the NVMe (or the group containing the NVMe) as the promote target, as that will be your primary cache drive.
"""
+lang: "en"
+isAdult: false
+favouriteCount: 1
+score: 0
+lastActive: DateTime @1699407312 {#1605
date: 2023-11-08 02:35:12.0 +01:00
}
+ip: null
+tags: [
"323232"
]
+mentions: [
"@Uluganda@lemmy.ml"
"@d3Xt3r@lemmy.nz"
]
+children: Doctrine\ORM\PersistentCollection {#2466 …}
+nested: Doctrine\ORM\PersistentCollection {#2288 …}
+votes: Doctrine\ORM\PersistentCollection {#2446 …}
+reports: Doctrine\ORM\PersistentCollection {#2439 …}
+favourites: Doctrine\ORM\PersistentCollection {#2489 …}
+notifications: Doctrine\ORM\PersistentCollection {#60 …}
-id: 100588
-bodyTs: "'/dev/nvme0n1':276 '/dev/sda':279 '/dev/sdb':282 '/dev/sdc':285 '/title/bcachefs)':239 '2':287 'also':177 'arch':235 'automat':319 'background':14,27,50,263,294 'bcachef':272,317 'becom':90 'benefit':187 'cach':84,126,266,385 'case':87 'caus':316 'chuck':302 'concern':300 'configur':245 'contain':372 'copi':62,71,85 'cours':174 'creat':207 'data':8,21,74,97,110,340 'differ':335 'drive':100,323,386 'either':112 'exampl':268 'faster':135,154,165,190 'final':69 'first':55 'foreground':1,12,45,141,161,183,228,254,288 'format':273 'full':91 'get':61,125 'go':7,56,358 'group':210,218,226,251,260,311,371 'hdd':65,116,259,296 'hdd.hdd1':281 'hdd.hdd2':284 'hdds':48,221 'idl':17,67 'illustr':240 'initi':6 'introduc':199 'io':350 'label':274,277,280,283 'latenc':326,351 'll':94 'lower':325 'lowest':349 'main':137,360 'mark':81 'mention':328 'mix':204 'modifi':267 'move':10,30 'need':20,313 'next':131 'nvme':38,122,159,170,180,213,307,368,374 'one':346 'plan':197 'point':138 'primari':384 'priorit':146,320 'promot':32,41,104,143,172,185,229,256,291,377 're':299 'read':24,109,132,149,166,191,321,337 'recommend':244 'regardless':353 'rememb':363 'replic':339 'replica':286 'scenario':271 'second':217 'sent':343 'set':36,157,168,178,223 'setup':356 'simplifi':232 'sinc':195 'singl':209 'speed':150,336 'ssd':43,59,77,89,114,201,214,225,250,290,293,305 'ssd.nvme1':275 'ssd.ssd1':278 'store':95 'target':2,15,28,33,42,51,105,289,292,295,378 'thing':233,361 'time':107 'use':248,366 'valu':153,164 'vs':142,148 'wasn':118 'well':242 'wiki':236,331 'wiki.archlinux.org':238 'wiki.archlinux.org/title/bcachefs)':237 'worri':315 'would':54,124 'write':5,53,147,155,193 'writeback':265"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.nz/comment/3610636"
+editedAt: DateTimeImmutable @1699454949 {#1945
date: 2023-11-08 15:49:09.0 +01:00
}
+createdAt: DateTimeImmutable @1699407312 {#1368
date: 2023-11-08 02:35:12.0 +01:00
}
} |
|
Show voter details
|
3 |
DENIED
|
edit
|
App\Entity\EntryComment {#1369
+user: Proxies\__CG__\App\Entity\User {#1370 …}
+entry: App\Entity\Entry {#1832 …}
+magazine: App\Entity\Magazine {#313
+icon: Proxies\__CG__\App\Entity\Image {#294 …}
+name: "linux@lemmy.ml"
+title: "linux"
+description: """
From Wikipedia, the free encyclopedia\n
\n
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).\n
\n
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.\n
\n
### Rules\n
\n
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.\n
- No misinformation\n
- No NSFW content\n
- No hate speech, bigotry, etc\n
\n
### Related Communities\n
\n
- [!opensource@lemmy.ml](https://lemmy.ml/c/opensource)\n
- [!libre_culture@lemmy.ml](https://lemmy.ml/c/libre_culture)\n
- [!technology@lemmy.ml](https://lemmy.ml/c/technology)\n
- [!libre_hardware@lemmy.ml](https://lemmy.ml/c/libre_hardware)\n
\n
Community icon by [Alpár-Etele Méder](https://www.iconfinder.com/pocike), licensed under [CC BY 3.0](https://creativecommons.org/licenses/by/3.0/)
"""
+rules: null
+subscriptionsCount: 1
+entryCount: 1406
+entryCommentCount: 28632
+postCount: 6
+postCommentCount: 214
+isAdult: false
+customCss: null
+lastActive: DateTime @1729583542 {#323
date: 2024-10-22 09:52:22.0 +02:00
}
+markedForDeletionAt: null
+tags: null
+moderators: Doctrine\ORM\PersistentCollection {#285 …}
+ownershipRequests: Doctrine\ORM\PersistentCollection {#281 …}
+moderatorRequests: Doctrine\ORM\PersistentCollection {#270 …}
+entries: Doctrine\ORM\PersistentCollection {#228 …}
+posts: Doctrine\ORM\PersistentCollection {#186 …}
+subscriptions: Doctrine\ORM\PersistentCollection {#248 …}
+bans: Doctrine\ORM\PersistentCollection {#165 …}
+reports: Doctrine\ORM\PersistentCollection {#151 …}
+badges: Doctrine\ORM\PersistentCollection {#129 …}
+logs: Doctrine\ORM\PersistentCollection {#119 …}
+awards: Doctrine\ORM\PersistentCollection {#108 …}
+categories: Doctrine\ORM\PersistentCollection {#95 …}
-id: 73
+apId: "linux@lemmy.ml"
+apProfileId: "https://lemmy.ml/c/linux"
+apPublicUrl: "https://lemmy.ml/c/linux"
+apFollowersUrl: "https://lemmy.ml/c/linux/followers"
+apInboxUrl: "https://lemmy.ml/inbox"
+apDomain: "lemmy.ml"
+apPreferredUsername: "linux"
+apDiscoverable: true
+apManuallyApprovesFollowers: null
+privateKey: null
+publicKey: null
+apFetchedAt: DateTime @1729583596 {#317
date: 2024-10-22 09:53:16.0 +02:00
}
+apDeletedAt: null
+apTimeoutAt: null
+visibility: "visible "
+createdAt: DateTimeImmutable @1698929468 {#316
date: 2023-11-02 13:51:08.0 +01:00
}
}
+image: null
+parent: Proxies\__CG__\App\Entity\EntryComment {#2451 …}
+root: Proxies\__CG__\App\Entity\EntryComment {#2356 …}
+body: """
Foreground targets are where writes initially go. Data is moved from foreground to background targets while idle or as needed. Data which is read from the background targets is moved to promote targets.\n
\n
If you set your NVMe as a promote target, SSD as foreground and your HDDs as background targets, all writes would first go to your SSD, then get copied to your HDD during idle, and finally the copy of the data on your SSD will then be marked as a cached copy. In case your SSD becomes full, then it’ll store the data on other drives. As for the promote targets, any time you read data from either the SSD or HDD that wasn’t on the NVMe, it would get cached to it, so the next read will be faster.\n
\n
The main point of the foreground vs promote is to prioritize write vs read speeds. If you value faster writes, then set your NVMe as foreground. If you value faster reads, then set your NVMe as promote. Of course, you can also set your NVMe as *both* foreground and promote to benefit from both faster reads and writes.\n
\n
But since you plan to introduce an SSD in the mix, you can create a single group for your NVMe + SSD, and a second group for the HDDs, and set your SSD group to foreground + promote, which will simplify things.\n
\n
The [Arch wiki](https://wiki.archlinux.org/title/Bcachefs) illustrates this well:\n
\n
> A recommended configuration is to use an ssd group for the foreground and promote, and an hdd group for the background (a writeback cache).\n
\n
Modified example to your scenario:\n
\n
```\n
\n
<span style="color:#323232;"># bcachefs format \n
</span><span style="color:#323232;"> --label=ssd.nvme1 /dev/nvme0n1 \n
</span><span style="color:#323232;"> --label=ssd.ssd1 /dev/sda \n
</span><span style="color:#323232;"> --label=hdd.hdd1 /dev/sdb \n
</span><span style="color:#323232;"> --label=hdd.hdd2 /dev/sdc \n
</span><span style="color:#323232;"> --replicas=2 \n
</span><span style="color:#323232;"> --foreground_target=ssd \n
</span><span style="color:#323232;"> --promote_target=ssd \n
</span><span style="color:#323232;"> --background_target=hdd \n
</span>\n
```\n
\n
If you’re concerned about chucking both the SSD and NVMe in the same group, no need to worry cause bcachefs will automatically prioritize reads from drives with lower latency as mentioned in the wiki.\n
\n
> If they are different speeds, reads for replicated data will be sent to the ones with the lowest IO latency.\n
\n
But regardless of which setup you go for, main thing to remember is to use the NVMe (or the group containing the NVMe) as the promote target, as that will be your primary cache drive.
"""
+lang: "en"
+isAdult: false
+favouriteCount: 1
+score: 0
+lastActive: DateTime @1699407312 {#1605
date: 2023-11-08 02:35:12.0 +01:00
}
+ip: null
+tags: [
"323232"
]
+mentions: [
"@Uluganda@lemmy.ml"
"@d3Xt3r@lemmy.nz"
]
+children: Doctrine\ORM\PersistentCollection {#2466 …}
+nested: Doctrine\ORM\PersistentCollection {#2288 …}
+votes: Doctrine\ORM\PersistentCollection {#2446 …}
+reports: Doctrine\ORM\PersistentCollection {#2439 …}
+favourites: Doctrine\ORM\PersistentCollection {#2489 …}
+notifications: Doctrine\ORM\PersistentCollection {#60 …}
-id: 100588
-bodyTs: "'/dev/nvme0n1':276 '/dev/sda':279 '/dev/sdb':282 '/dev/sdc':285 '/title/bcachefs)':239 '2':287 'also':177 'arch':235 'automat':319 'background':14,27,50,263,294 'bcachef':272,317 'becom':90 'benefit':187 'cach':84,126,266,385 'case':87 'caus':316 'chuck':302 'concern':300 'configur':245 'contain':372 'copi':62,71,85 'cours':174 'creat':207 'data':8,21,74,97,110,340 'differ':335 'drive':100,323,386 'either':112 'exampl':268 'faster':135,154,165,190 'final':69 'first':55 'foreground':1,12,45,141,161,183,228,254,288 'format':273 'full':91 'get':61,125 'go':7,56,358 'group':210,218,226,251,260,311,371 'hdd':65,116,259,296 'hdd.hdd1':281 'hdd.hdd2':284 'hdds':48,221 'idl':17,67 'illustr':240 'initi':6 'introduc':199 'io':350 'label':274,277,280,283 'latenc':326,351 'll':94 'lower':325 'lowest':349 'main':137,360 'mark':81 'mention':328 'mix':204 'modifi':267 'move':10,30 'need':20,313 'next':131 'nvme':38,122,159,170,180,213,307,368,374 'one':346 'plan':197 'point':138 'primari':384 'priorit':146,320 'promot':32,41,104,143,172,185,229,256,291,377 're':299 'read':24,109,132,149,166,191,321,337 'recommend':244 'regardless':353 'rememb':363 'replic':339 'replica':286 'scenario':271 'second':217 'sent':343 'set':36,157,168,178,223 'setup':356 'simplifi':232 'sinc':195 'singl':209 'speed':150,336 'ssd':43,59,77,89,114,201,214,225,250,290,293,305 'ssd.nvme1':275 'ssd.ssd1':278 'store':95 'target':2,15,28,33,42,51,105,289,292,295,378 'thing':233,361 'time':107 'use':248,366 'valu':153,164 'vs':142,148 'wasn':118 'well':242 'wiki':236,331 'wiki.archlinux.org':238 'wiki.archlinux.org/title/bcachefs)':237 'worri':315 'would':54,124 'write':5,53,147,155,193 'writeback':265"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.nz/comment/3610636"
+editedAt: DateTimeImmutable @1699454949 {#1945
date: 2023-11-08 15:49:09.0 +01:00
}
+createdAt: DateTimeImmutable @1699407312 {#1368
date: 2023-11-08 02:35:12.0 +01:00
}
} |
|
Show voter details
|
4 |
DENIED
|
moderate
|
App\Entity\EntryComment {#1369
+user: Proxies\__CG__\App\Entity\User {#1370 …}
+entry: App\Entity\Entry {#1832 …}
+magazine: App\Entity\Magazine {#313
+icon: Proxies\__CG__\App\Entity\Image {#294 …}
+name: "linux@lemmy.ml"
+title: "linux"
+description: """
From Wikipedia, the free encyclopedia\n
\n
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).\n
\n
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.\n
\n
### Rules\n
\n
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.\n
- No misinformation\n
- No NSFW content\n
- No hate speech, bigotry, etc\n
\n
### Related Communities\n
\n
- [!opensource@lemmy.ml](https://lemmy.ml/c/opensource)\n
- [!libre_culture@lemmy.ml](https://lemmy.ml/c/libre_culture)\n
- [!technology@lemmy.ml](https://lemmy.ml/c/technology)\n
- [!libre_hardware@lemmy.ml](https://lemmy.ml/c/libre_hardware)\n
\n
Community icon by [Alpár-Etele Méder](https://www.iconfinder.com/pocike), licensed under [CC BY 3.0](https://creativecommons.org/licenses/by/3.0/)
"""
+rules: null
+subscriptionsCount: 1
+entryCount: 1406
+entryCommentCount: 28632
+postCount: 6
+postCommentCount: 214
+isAdult: false
+customCss: null
+lastActive: DateTime @1729583542 {#323
date: 2024-10-22 09:52:22.0 +02:00
}
+markedForDeletionAt: null
+tags: null
+moderators: Doctrine\ORM\PersistentCollection {#285 …}
+ownershipRequests: Doctrine\ORM\PersistentCollection {#281 …}
+moderatorRequests: Doctrine\ORM\PersistentCollection {#270 …}
+entries: Doctrine\ORM\PersistentCollection {#228 …}
+posts: Doctrine\ORM\PersistentCollection {#186 …}
+subscriptions: Doctrine\ORM\PersistentCollection {#248 …}
+bans: Doctrine\ORM\PersistentCollection {#165 …}
+reports: Doctrine\ORM\PersistentCollection {#151 …}
+badges: Doctrine\ORM\PersistentCollection {#129 …}
+logs: Doctrine\ORM\PersistentCollection {#119 …}
+awards: Doctrine\ORM\PersistentCollection {#108 …}
+categories: Doctrine\ORM\PersistentCollection {#95 …}
-id: 73
+apId: "linux@lemmy.ml"
+apProfileId: "https://lemmy.ml/c/linux"
+apPublicUrl: "https://lemmy.ml/c/linux"
+apFollowersUrl: "https://lemmy.ml/c/linux/followers"
+apInboxUrl: "https://lemmy.ml/inbox"
+apDomain: "lemmy.ml"
+apPreferredUsername: "linux"
+apDiscoverable: true
+apManuallyApprovesFollowers: null
+privateKey: null
+publicKey: null
+apFetchedAt: DateTime @1729583596 {#317
date: 2024-10-22 09:53:16.0 +02:00
}
+apDeletedAt: null
+apTimeoutAt: null
+visibility: "visible "
+createdAt: DateTimeImmutable @1698929468 {#316
date: 2023-11-02 13:51:08.0 +01:00
}
}
+image: null
+parent: Proxies\__CG__\App\Entity\EntryComment {#2451 …}
+root: Proxies\__CG__\App\Entity\EntryComment {#2356 …}
+body: """
Foreground targets are where writes initially go. Data is moved from foreground to background targets while idle or as needed. Data which is read from the background targets is moved to promote targets.\n
\n
If you set your NVMe as a promote target, SSD as foreground and your HDDs as background targets, all writes would first go to your SSD, then get copied to your HDD during idle, and finally the copy of the data on your SSD will then be marked as a cached copy. In case your SSD becomes full, then it’ll store the data on other drives. As for the promote targets, any time you read data from either the SSD or HDD that wasn’t on the NVMe, it would get cached to it, so the next read will be faster.\n
\n
The main point of the foreground vs promote is to prioritize write vs read speeds. If you value faster writes, then set your NVMe as foreground. If you value faster reads, then set your NVMe as promote. Of course, you can also set your NVMe as *both* foreground and promote to benefit from both faster reads and writes.\n
\n
But since you plan to introduce an SSD in the mix, you can create a single group for your NVMe + SSD, and a second group for the HDDs, and set your SSD group to foreground + promote, which will simplify things.\n
\n
The [Arch wiki](https://wiki.archlinux.org/title/Bcachefs) illustrates this well:\n
\n
> A recommended configuration is to use an ssd group for the foreground and promote, and an hdd group for the background (a writeback cache).\n
\n
Modified example to your scenario:\n
\n
```\n
\n
<span style="color:#323232;"># bcachefs format \n
</span><span style="color:#323232;"> --label=ssd.nvme1 /dev/nvme0n1 \n
</span><span style="color:#323232;"> --label=ssd.ssd1 /dev/sda \n
</span><span style="color:#323232;"> --label=hdd.hdd1 /dev/sdb \n
</span><span style="color:#323232;"> --label=hdd.hdd2 /dev/sdc \n
</span><span style="color:#323232;"> --replicas=2 \n
</span><span style="color:#323232;"> --foreground_target=ssd \n
</span><span style="color:#323232;"> --promote_target=ssd \n
</span><span style="color:#323232;"> --background_target=hdd \n
</span>\n
```\n
\n
If you’re concerned about chucking both the SSD and NVMe in the same group, no need to worry cause bcachefs will automatically prioritize reads from drives with lower latency as mentioned in the wiki.\n
\n
> If they are different speeds, reads for replicated data will be sent to the ones with the lowest IO latency.\n
\n
But regardless of which setup you go for, main thing to remember is to use the NVMe (or the group containing the NVMe) as the promote target, as that will be your primary cache drive.
"""
+lang: "en"
+isAdult: false
+favouriteCount: 1
+score: 0
+lastActive: DateTime @1699407312 {#1605
date: 2023-11-08 02:35:12.0 +01:00
}
+ip: null
+tags: [
"323232"
]
+mentions: [
"@Uluganda@lemmy.ml"
"@d3Xt3r@lemmy.nz"
]
+children: Doctrine\ORM\PersistentCollection {#2466 …}
+nested: Doctrine\ORM\PersistentCollection {#2288 …}
+votes: Doctrine\ORM\PersistentCollection {#2446 …}
+reports: Doctrine\ORM\PersistentCollection {#2439 …}
+favourites: Doctrine\ORM\PersistentCollection {#2489 …}
+notifications: Doctrine\ORM\PersistentCollection {#60 …}
-id: 100588
-bodyTs: "'/dev/nvme0n1':276 '/dev/sda':279 '/dev/sdb':282 '/dev/sdc':285 '/title/bcachefs)':239 '2':287 'also':177 'arch':235 'automat':319 'background':14,27,50,263,294 'bcachef':272,317 'becom':90 'benefit':187 'cach':84,126,266,385 'case':87 'caus':316 'chuck':302 'concern':300 'configur':245 'contain':372 'copi':62,71,85 'cours':174 'creat':207 'data':8,21,74,97,110,340 'differ':335 'drive':100,323,386 'either':112 'exampl':268 'faster':135,154,165,190 'final':69 'first':55 'foreground':1,12,45,141,161,183,228,254,288 'format':273 'full':91 'get':61,125 'go':7,56,358 'group':210,218,226,251,260,311,371 'hdd':65,116,259,296 'hdd.hdd1':281 'hdd.hdd2':284 'hdds':48,221 'idl':17,67 'illustr':240 'initi':6 'introduc':199 'io':350 'label':274,277,280,283 'latenc':326,351 'll':94 'lower':325 'lowest':349 'main':137,360 'mark':81 'mention':328 'mix':204 'modifi':267 'move':10,30 'need':20,313 'next':131 'nvme':38,122,159,170,180,213,307,368,374 'one':346 'plan':197 'point':138 'primari':384 'priorit':146,320 'promot':32,41,104,143,172,185,229,256,291,377 're':299 'read':24,109,132,149,166,191,321,337 'recommend':244 'regardless':353 'rememb':363 'replic':339 'replica':286 'scenario':271 'second':217 'sent':343 'set':36,157,168,178,223 'setup':356 'simplifi':232 'sinc':195 'singl':209 'speed':150,336 'ssd':43,59,77,89,114,201,214,225,250,290,293,305 'ssd.nvme1':275 'ssd.ssd1':278 'store':95 'target':2,15,28,33,42,51,105,289,292,295,378 'thing':233,361 'time':107 'use':248,366 'valu':153,164 'vs':142,148 'wasn':118 'well':242 'wiki':236,331 'wiki.archlinux.org':238 'wiki.archlinux.org/title/bcachefs)':237 'worri':315 'would':54,124 'write':5,53,147,155,193 'writeback':265"
+ranking: 0
+commentCount: 0
+upVotes: 0
+downVotes: 0
+visibility: "visible "
+apId: "https://lemmy.nz/comment/3610636"
+editedAt: DateTimeImmutable @1699454949 {#1945
date: 2023-11-08 15:49:09.0 +01:00
}
+createdAt: DateTimeImmutable @1699407312 {#1368
date: 2023-11-08 02:35:12.0 +01:00
}
} |
|
Show voter details
|
5 |
DENIED
|
edit
|
App\Entity\Magazine {#313
+icon: Proxies\__CG__\App\Entity\Image {#294 …}
+name: "linux@lemmy.ml"
+title: "linux"
+description: """
From Wikipedia, the free encyclopedia\n
\n
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).\n
\n
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.\n
\n
### Rules\n
\n
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.\n
- No misinformation\n
- No NSFW content\n
- No hate speech, bigotry, etc\n
\n
### Related Communities\n
\n
- [!opensource@lemmy.ml](https://lemmy.ml/c/opensource)\n
- [!libre_culture@lemmy.ml](https://lemmy.ml/c/libre_culture)\n
- [!technology@lemmy.ml](https://lemmy.ml/c/technology)\n
- [!libre_hardware@lemmy.ml](https://lemmy.ml/c/libre_hardware)\n
\n
Community icon by [Alpár-Etele Méder](https://www.iconfinder.com/pocike), licensed under [CC BY 3.0](https://creativecommons.org/licenses/by/3.0/)
"""
+rules: null
+subscriptionsCount: 1
+entryCount: 1406
+entryCommentCount: 28632
+postCount: 6
+postCommentCount: 214
+isAdult: false
+customCss: null
+lastActive: DateTime @1729583542 {#323
date: 2024-10-22 09:52:22.0 +02:00
}
+markedForDeletionAt: null
+tags: null
+moderators: Doctrine\ORM\PersistentCollection {#285 …}
+ownershipRequests: Doctrine\ORM\PersistentCollection {#281 …}
+moderatorRequests: Doctrine\ORM\PersistentCollection {#270 …}
+entries: Doctrine\ORM\PersistentCollection {#228 …}
+posts: Doctrine\ORM\PersistentCollection {#186 …}
+subscriptions: Doctrine\ORM\PersistentCollection {#248 …}
+bans: Doctrine\ORM\PersistentCollection {#165 …}
+reports: Doctrine\ORM\PersistentCollection {#151 …}
+badges: Doctrine\ORM\PersistentCollection {#129 …}
+logs: Doctrine\ORM\PersistentCollection {#119 …}
+awards: Doctrine\ORM\PersistentCollection {#108 …}
+categories: Doctrine\ORM\PersistentCollection {#95 …}
-id: 73
+apId: "linux@lemmy.ml"
+apProfileId: "https://lemmy.ml/c/linux"
+apPublicUrl: "https://lemmy.ml/c/linux"
+apFollowersUrl: "https://lemmy.ml/c/linux/followers"
+apInboxUrl: "https://lemmy.ml/inbox"
+apDomain: "lemmy.ml"
+apPreferredUsername: "linux"
+apDiscoverable: true
+apManuallyApprovesFollowers: null
+privateKey: null
+publicKey: null
+apFetchedAt: DateTime @1729583596 {#317
date: 2024-10-22 09:53:16.0 +02:00
}
+apDeletedAt: null
+apTimeoutAt: null
+visibility: "visible "
+createdAt: DateTimeImmutable @1698929468 {#316
date: 2023-11-02 13:51:08.0 +01:00
}
} |
|
Show voter details
|